Here's the story, since I gather not everyone reads the mapguide-users mailing list where I mentioned this subject many months ago.
I've decided (many months ago) to skip on making this release.
The differences between 3.1 and (a 3.2 release if I had decided to make one) is so small that it isn't worth investing the build resources on a 3.2 release cycle.
Since I'm skipping on a 3.2 release, it means that we have a good year-long window of solid development time to get some compelling features into the release after it (currently set as 3.3). Some of this development work is already starting to bear fruit.
Now that's not to say there isn't going to be a MapGuide release sometime between now and when 3.3 is out. I still do hope to put out the (hinted previously) patch releases for MGOS 2.6, 3.0 and 3.1 in between, but that requires me rebuilding my build infrastructure first and that is currently taking a back seat to landing some solid features into 3.3 first, so that's where things are at.
And as always. As these features land, you can expect this blog to talk about it.
Posts
Upcoming Changes to InfraWorks Services
6 years ago
3 comments:
Worth the wait! Can't wait to see what ends up in 3.3.
Hi all, Any news on the 3.3 release date?
Wondering if any thing will change now that Autodesk announced the Infrastructure Map Server End of Life.
No news on a 3.3 release date, because I still have a pipeline of new features I want to get into this release.
Autodesk EOLing Infrastructure Map Server has not changed these plans.
Post a Comment