[mapguide-internals] MGOS 2.1 branch

Jason Birch Jason.Birch at nanaimo.ca
Mon May 11 01:38:38 EDT 2009

Oh, branching a level up?  I guess that would work, but Maestro is on a totally different release cycle than MapGuide.  You could just create the 2.1.x branch, and then branch the individual Installer and MgDev folders inside of that.  Then tagging the branch with releases would at least be fairly easy.  

Of course, it may just be easier to move the installer inside of MgDev :)  That would mean pulling the Maestro installer tech out of there, but that should probably be cleaned up anyway.  I don't think Kenneth is using it, and it's not had any attention from me or Jackie since we decided to pull Maestro from the MapGuide installer.

Ideally, I would like to see a system where the installer is part of the CI process, and developers are responsible for working to resolve cases where the installer breaks because of their code changes.  Making the installer part of MgDev may help to enforce this attitude/expectation.

From: Tom Fukushima
Sent: Sunday, May 10, 2009 8:23 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MGOS 2.1 branch

If no one finds a problem with it, I would like to put Installer, MgDev and Tools into the 2.1 branch.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Friday, May 08, 2009 1:40 PM
To: 'mapguide-internals at lists.osgeo.org'
Subject: Re: [mapguide-internals] MGOS 2.1 branch

No real concerns with this, but would love to see Trevor's upcoming fixes make it into the 2.1 branch.

Should we move the installer code inside of mgdev so it comes along for the ride with branches/tags, or should we branch/tag seperately?

----- Original Message -----
From: mapguide-internals-bounces at lists.osgeo.org <mapguide-internals-bounces at lists.osgeo.org>
To: MapGuide Internals Mail List <mapguide-internals at lists.osgeo.org>
Sent: Thu May 07 14:36:02 2009
Subject: [mapguide-internals] MGOS 2.1 branch


There is some work in the CsMap trunk that is going to get underway and will require some changes to MGOS.  The changes should not go into MGOS 2.1 because they require large changes, so I would like to create the MGOS 2.1 branch on the week of May 18th.

After the branch the difference between Trunk and the 2.1 branch will be that branch will (continue to) point to CsMap branch 12.01, and trunk will point to CsMap trunk.

Any questions or concerns?

mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list