[mapguide-internals] RE: PATCH: Raster stability fixes, ticket#462

Martin Morrison martin.morrison at edsi.com
Tue Mar 31 12:29:30 EDT 2009


It was not my intention to come across as not working on raster.  Raster is a big deal.  If anything, we need to focus on it.  My point was we shouldn't hold it back.  When I talked about 2.11, 2.12, etc the intent was not for it to be pushed out a year at a time, I would picture these coming fairly quickly.  A month or so at a time...

Too many times developers are under pressure from marketing/upper management to deliver new features and fix the bugs later.  This is wrong.  Stability should be at the top of everyone's mind now.  But it is my understanding that 2.1 has fixes for stability, therefore let's get it out.


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Tuesday, March 31, 2009 12:18 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RE: PATCH: Raster stability fixes, ticket#462

At this point I don't have the energy to fight to have it held back.  After deciding on an appropriate temporary workaround (I'm still leaning towards the big guard), we'll just have to see how the beta testing goes and make a decision based on those results.  

I do worry that moving ahead like this will remove the impetus for change.  Other issues (permissions, security, etc) have languished because while they are important they haven't been made urgent.


-----Original Message-----
From: Bruce Dechant
Sent: March-30-09 12:20 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RE: PATCH: Raster stability fixes, ticket#462


I understand the situation and fully agree that the GDAL provider is very important to MapGuide.
I sure hope no one has to wait a whole year for this to be fixed properly. I think it has only been recently that we now have a much better understanding of what the actual issue is and what is causing the instability.

2.1 has lots of improvements and I was hoping we could get it in the users hands as planned, but if the PSC feels that this is a stop release issue then the PSC needs to make that call and postpone the release until this issue is addressed properly. 

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

More information about the mapguide-internals mailing list