[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-devel
Subject:    Re: [postgis-devel] PSC Vote: PostGIS 2.2.1 release in 2 weeks
From:       "Paragon Corporation" <lr () pcorp ! us>
Date:       2016-01-06 14:18:25
Message-ID: 000401d1488d$1b2d0960$51871c20$ () pcorp ! us
[Download RAW message or body]

Greg,

I'm listening.  I would actually like that too.  I'm just not sure we are
disciplined enough for that.  I'm not sure I'm that disciplined at anyrate.
So temping to make doc changes right before release.

Maybe we can try that approach when we release 2.1.9 and 2.0.8  in  say
about 2 to 3 weeks time.

I'm thinking it would work like this:

1) Do all our work in branch. 
2) Change the version number to release version number
3) Declare freeze on changes
4) Wait a couple of days -- 3 days feels about right
5) Then make the tagged release tarball.
6) Announce

Is that what you had in mind?

Thanks,
Regina
-----Original Message-----
From: Greg Troxel [mailto:gdt@ir.bbn.com] 
Sent: Wednesday, January 06, 2016 8:32 AM
To: Paragon Corporation <lr@pcorp.us>
Cc: 'PostGIS Development Discussion' <postgis-devel@lists.osgeo.org>
Subject: Re: [postgis-devel] PSC Vote: PostGIS 2.2.1 release in 2 weeks


I'd like to object to making changes during what should be the pre-release
freeze period, and then having a rushed release.  I don't really expect
anyone to listen to me, but for the record...


_______________________________________________
postgis-devel mailing list
postgis-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/postgis-devel
[prev in list] [next in list] [prev in thread] [next in thread]