[postgis-devel] [PostGIS] #1472: Get out a tagged release
PostGIS
trac at osgeo.org
Sun Jan 15 13:10:10 PST 2012
#1472: Get out a tagged release
------------------------+---------------------------------------------------
Reporter: robe | Owner: pramsey
Type: task | Status: new
Priority: medium | Milestone: PostGIS 2.0.0
Component: management | Version: trunk
Keywords: |
------------------------+---------------------------------------------------
It seems we are not brave enough to stamp a tagged release as alpha. Not
sure why the hesitation. At this point I'll take anything as long as its
tagged. Forget about feature freeze, we can keep on making changes till
the end and just push anything we don't get to to the next version as long
as people have a clear idea of whether they need to dump reload and what
things are very stable.
However I am concerned about the number of people who I have come across
that are using 2.0 in production. I think we owe it to them for their
bravery to at least start getting out some tagged versions so that when it
comes time to release 2.0, everyone will know if they need to do a full
dump /restore and our dump restore can account for people upgrading from
non-production releases.
It will also allow us to stream line the upgrade process a bit by checking
version numbers and conditionally put in things we need to be done for one
alpha and not another. Which will probably solve strk's issue with
aggregates as I do think we should only conditionally drop / create
aggregates if needed.
Also doing things like making sure our tar balls etc are in a state where
package managers can use them without fuss. Greg Troxel has already
started to do this and outlining issues (thanks Greg).
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1472>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list