[mapguide-internals] MGOS 2.0 beta

[Jason Birch]

Wow,
 
Well, I did a bit of stuff, and am feeling a bit overwhelmed.
 
I don't know enough about what has already been done to question whether tickets are outstanding or need to be closed.  I went and removed milestones from a few tasks that didn't have assignees, but then I ran into some that I was pretty sure were being worked on but had no assignee, so stopped doing that.
 
I think that this needs a general sanity-check by someone familiar with current development status, especially removing the milestone from tickets that don't currently have development resources assigned to them.  Then, from all of the outstanding bugs, I think we can prioritise more easily.  
 
Obviously, enhancements will have to wait until at least 2.1 at this point.  There are a few issues that stand out for sure though.
 
Jason

________________________________

From: mapguide-internals-bounces at lists.osgeo.org on behalf of Jason Birch
Sent: Tue 2007-10-16 2:22 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MGOS 2.0 beta



> Maybe for now, we just enlist the common sense of one of the
> community members... Jason, would you be able to go through
> them and prioritize the tickets? Does this sound reasonable?

Are you feeling OK? ;)

I'll see if I can get this done.  Can I ask the audience?  I know I saw
a post about a user being unable to implement with 1.2 because of an
outstanding bug.

Jason
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals