[mapguide-internals] Next release: 2.4.1 or straight to 2.5?

[Zac Spitzer]

+1 for moving straight to 2.5

I'm a fan of release early, release often, especially given limited
resources


On Sat, Dec 8, 2012 at 11:56 PM, Jackie Ng <jumpinjackie at gmail.com> wrote:

> Hi All,
>
> In the interest of releasing early and more often, I want to start
> discussions on what our next release should be. Should we look at putting
> out a 2.4.1 bugfix release or go straight to 2.5?
>
> I'm leaning to going straight to 2.5 for the simple reasons:
>
>  * Lots of FDO provider fixes and improvements that simply cannot be
> backported to 2.4 (ie. SQL Server fubar and Trevor's GDAL provider
> resampling). The SQL Server story in 2.4 is quite bad, which a rapid 2.5
> release cycle could rectify.
>  * Less "catch up" with Autodesk's commercial releases of the same
> milestone. The MGOS releases have historically lagged significantly behind
> the commercial ones.
>
> Thoughts?
>
> - Jackie
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.n6.nabble.com/Next-release-2-4-1-or-straight-to-2-5-tp5021598.html
> Sent from the MapGuide Internals mailing list archive at Nabble.com.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
+61 405 847 168