[mapguide-internals] MapGuide 2.3 and FOSS4G 2011

Fri Jun 10 08:26:50 EDT 2011

Hi trevor,

rfc90 will simply introduce an optional  serverconfig.ini variable to 
specify the metatiling factor.
So no API changes here.

However, in the future an extensions for the  baselayergroup xml 
specifying  the imagetype and metatiling factor per baselayergroup could 
be introduced to maximize effects.

On 10/06/2011 07:39, Trevor Wekel wrote:
> Hi Zac,
>
> Should we roll out a 2.2.1 patch before the 2.3 beta?  I think we already have a laundry list of fixes that need to go in - not the least of which is IE9 support for Ajax and Fusion.  Microsoft is already pushing IE9 through Windows Update.
>
> Ideally, we should craft a 2.3 release that is similar to AIMS 2012.  This would mean rolling out something similar to trunk.  Does the meta tiling affect any public APIs?  If not, it would be good to get it in.
>
> Also for 2.3, I would like take a run at gcc 4.4 for Linux.  This would give us native builds on Ubuntu 10.04 LTS and RedHat 6.   Hopefully this will get us native on OSGeo-Live as well (Ubuntu 11).  64 bit would be a bonus too assuming I have time.  I could find more time if "the community" wanted to fund the work.
>
> The six items you mentioned below are definitely 2.4 items.  Autodesk will need some lead time to figure out how to incorporate them into AIMS.
>
> Gcc 4.4 and 64 bit for Linux will eat up all of my free time.  If we want this for 2.3, someone else will have to take on the builds and "project management" pieces for 2.3.  I was chatting with Martin Morrison a while back and he showed some interest in helping out.  I can set up SSL VPN access to the builds infrastructure for anyone who wants it.
>
> You raise an interesting point about dropping 2.3 and simply moving to 2.4.  Do we really need to release something "similar to" AIMS 2012?  Maybe not.  On the other hand, it would be good to get a native build on OSGeo-Live for FOSS4G 2011.  This means the gcc 4.4 (32 bit) work would have to get done by early next month.  Unfortunately, the 2.2 Oem tree is not gcc 4.4 friendly.  I believe trunk Oem is.  I was going to start looking at this tomorrow to see how bad it is.
>
> The key dates for OSGeo-Live are:
>
> Feature Freeze July 4
> - "Final" app versions must be installed
> - Minor bug fixes can be put in after feature freeze assuming the install image is the same
>
> English Documentation Complete July 18
> - We already have the docs available from last time.  Some edits may be required.
>
> Final ISO for OSGeo-Live August 22
>
>
> Regards,
> Trevor
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
> Sent: June 9, 2011 10:08 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] MapGuide 2.3 and FOSS4G 2011
>
> Hi Trevor,
>
> As the 2.2 build process did drag out a very long time, as has the
> proposed Beta date is already passed.
>
> I would like to propose we wait for Uv to finish the meta-tiling RFC
> which he is close to have complete before we beta 2.3.
>
> for 2.4 I want to rev the mapDefinition schema's to support nice things like
>
> 1. image format (per map and base layer group),
> 2. jpeg compression,
> 3. quantize alogoriuthms
> 4. meta tiling factor  (per map and base layer group),
> 5. selection color
> 6. tile cache expiry headers
>
> via an options xml approach which is extensible
>
> This will resolve most of the underlying annoyances relating
> to serverconfig.ini settings not being tuneable per map.
>
> The swear jar at Ennoble's office will suffer a huge loss of
> donations after this.
>
> I would like to push 2.4 out the door quickly to get these
> frustrating limitations in MapGuide eliminated.
>
> Or do we simply skip 2.3 and move to a 2.4 release
>
> z
>
> On Mon, Mar 14, 2011 at 2:17 AM, Trevor Wekel
> <trevor_wekel at otxsystems.com>  wrote:
>> Hi list,
>>
>> FOSS4G 2011 is being held in Denver this year on September 12th to 16th.  One of the deliverables for FOSS4G is the OSGeo Live DVD.  MapGuide is present on the DVD.  To get the DVD burned before the conference starts, all projects on the DVD need to have final versions of their product(s) ready by mid-August.  From the project schedule http://spreadsheets.google.com/ccc?key=tMRaCwabv7SiIG3moHEfMrQ&hl=en_GB# they will be targeting Ubuntu 11 as the platform.
>>
>> I think native compilation on Ubuntu 11 (32bit?) will be required for a successful deployment due to changing versions of distro packages used by FDO and MapGuide.  I believe we will also need to base our code drop on MapGuide trunk and FDO 3.6.  The recent library upgrades (Berkeley DB mostly) will get us closer to native compilation.  Ideally, the binaries on OSGeo Live should be officially released software.
>>
>> MapGuide 2.2 is nearly out the door (I'm about to start the RC4 build...) so a MapGuide 2.3 release in August would be roughly six months between releases.  If we work back from a 2.3 Final in mid-August with two weeks between RCs and a 1 month beta, the timeline would look something like:
>>
>> June 6 MapGuide 2.3 Beta
>> July 4 MapGuide 2.3 RC1
>> July 18 MapGuide 2.3 RC2
>> August 1 MapGuide 2.3 RC3
>> August 15 MapGuide 2.3 Final Release
>>
>> Based on some offline feedback I have received from the community, it would be good to provide binaries for the following platforms:
>>
>> Windows 32bit
>> Windows 64bit
>> RHEL 5 32bit
>> RHEL 6 32bit
>> Ubuntu 10.04 LTS 32 bit
>> Ubuntu 11 32 bit (for OSGeo Live)
>>
>> (stretch goal - add 64 bit for Linux)
>> RHEL 5 64bit
>> RHEL 6 64bit
>> Ubuntu 10.04 LTS 64 bit
>>
>> Additional hardware purchases (ie. another server) will give us enough capacity to handle all these platforms.  The real question comes down to developer resources.  This will be a monumental undertaking, especially since we need to do FDO and MapGuide builds.  That's a total of 18 builds (MapGuide and FDO on 9 platforms each).  If we factor in automation, Windows installers and Linux rpm/deb packagers this feels like a six month commitment for a senior developer.  Unfortunately, this would also be six months of unpaid work since our Sponsorship program hasn't taken off yet.
>>
>>
>> Do we want to do this?
>>
>> Can we do this?
>>
>>
>> Regards,
>> Trevor
>>
>>
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>>
>
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals