[postgis-devel] Vote to call Feature Freeze, SRID=0, and officially tag the first alpha

[Paragon Corporation]

Mark,

Just realized I had a typo.  By alright, meant already in trac.

Do you have this in trac already?  If not please get it in there.

Also what is your vote on other items.

I think Paul already pushed to push til 1/5th 2011.

Perhaps we should define better what alpha means.

To me it means not all stuff may be in there, but I can count on what is
there working 
if I start using it and working at release time and I have a fairly clear
idea of what I will be getting in 2.0 
so I can make plans and that we have a freeze point we can easily point at
and say from this point
forward -- you'll be okay to do a soft uprade.

So your main stickling issue I see, is I don't see anything under trac
loader/dumper assigned to you that sounds anything remotely to what you are
talking about and slated for 2.0.0. Please get it in there if it isn't
already.


Thanks,
Regina
 

> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net 
> [mailto:postgis-devel-bounces at postgis.refractions.net] On 
> Behalf Of Mark Cave-Ayland
> Sent: Thursday, December 29, 2011 6:03 PM
> To: postgis-devel at postgis.refractions.net
> Subject: Re: [postgis-devel] Vote to call Feature Freeze, 
> SRID=0, and officially tag the first alpha
> 
> On 20/12/11 23:43, Paragon Corporation wrote:
> 
> > I think enough people are using PostGIS 2.0.0 that its 
> about time to 
> > put out an official alpha 1 and also call feature freeze.
> >
> > By feature freeze, I mean anything that is not alright in our trac 
> > will have to wait or anything that will require anyone 
> already running 
> > the latest PostGIS 2.0.0 development to do a full dump 
> reload will also have to wait.
> > The only exception is if we find a critical issue that 
> requires us to 
> > make changes that require a dump reload.
> >
> >
> > +1 feature freeze
> > +1 SRID=0 be unknown (hey most of our code is already coded 
> that way 
> > +and
> > more people are whining about how we haven't made an 
> official decision 
> > than what decision we make.  I suspect many e.g GDAL have 
> already made 
> > provisions for this change, and many other tools don't even 
> work with 
> > unknown SRIDs)
> > +1 tag the first official alpha
> 
> Hi everyone,
> 
> In terms of a freeze, I'm still working on fixing up the 
> loader GUI based upon Mark's changes. Having spent most of 
> today on this, there is still a good couple of days work 
> involved to detangle various bits of code. The main issues I 
> am working on are:
> 
> 1) Instead of passing around structures, the existing code 
> manipulates the GUI directly in multiple places. This makes 
> it harder to add new flags etc. since the logic is no longer 
> in one place.
> 
> 2) To add to 1) above, the code introduces a new FILENODE 
> type to shadow SHPLOADERCONFIG when in fact this should be 
> completely removed and a linked list of SHPLOADERCONFIGs used instead.
> 
> 3) Adding dumper support.
> 
> 4) Remove the large number of Gtk assertions thrown on the 
> console during normal operation.
> 
> I suspect it's going to take a good solid couple of days to 
> finish off the reworking of this section of code and get it 
> somewhere towards a committable state. I'd like to get this 
> done sooner rather than later as it will make ongoing 
> maintenance much easier...
> 
> 
> ATB,
> 
> Mark.
> 
> --
> Mark Cave-Ayland - Senior Technical Architect PostgreSQL - 
> PostGIS Sirius Corporation plc - control through freedom 
> http://www.siriusit.co.uk
> t: +44 870 608 0063
> 
> Sirius Labs: http://www.siriusit.co.uk/labs 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>