MapGuide 2.1 Status

2 messages Options
Embed this post
Permalink
Crispin_at_1Spatial

MapGuide 2.1 Status

Reply Threaded More More options
Print post
Permalink
Hi,

I am not sure if the PSC met or not this week but for a couple of agendas now the 2.1 release has not been on the list.  There was a big discussion about 3 months ago about the raster resolution "big block" that I thought was designed to provide a way forward on the blocker issues for a release.

Whilst I appreciate there is a lot of work on RFCs and there is a team doing good-stuff I wonder if when the project is trac'd as "3 months late" (put back from an earlier date) there should be a report to the community - for us to keep the faith that this will not be a perpetual beta like some other projects.

The last code-drop to the 2.1 trunk was a couple of weeks ago and the beta is 6-weeks old.  Notwithstanding the interesting stress-test results from Bruce will the 9 "high" priority issues be addressed in any known timescale or need to be re-triarged?

Thanks for any information forthcoming...

 Crispin
Kenneth Skovhede, GEOGRAF A/S

Re: MapGuide 2.1 Status

Reply Threaded More More options
Print post
Permalink
The PSC did not meet this week.

I hope the PSC will meet this thursday, and I have put your items on the
agenda:
http://trac.osgeo.org/mapguide/wiki/PscMeeting07-09-2009

Regards, Kenneth Skovhede, GEOGRAF A/S



Crispin_at_1Spatial skrev:

> Hi,
>
> I am not sure if the PSC met or not this week but for a couple of agendas
> now the 2.1 release has not been on the list.  There was a big discussion
> about 3 months ago about the raster resolution "big block" that I thought
> was designed to provide a way forward on the blocker issues for a release.
>
> Whilst I appreciate there is a lot of work on RFCs and there is a team doing
> good-stuff I wonder if when the project is trac'd as "3 months late" (put
> back from an earlier date) there should be a report to the community - for
> us to keep the faith that this will not be a perpetual beta like some other
> projects.
>
> The last code-drop to the 2.1 trunk was a couple of weeks ago and the beta
> is 6-weeks old.  Notwithstanding the interesting stress-test results from
> Bruce will the 9 "high" priority issues be addressed in any known timescale
> or need to be re-triarged?
>
> Thanks for any information forthcoming...
>
>  Crispin
>
>  
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals