Tom Lane <t...@sss.pgh.pa.us> writes: > I think it'd likely be sufficient to bump them only once per release > cycle, ie, there's no need to distinguish versions that never appeared > in the wild. But if we forgot and created 1.1 early in the 9.2 release > cycle and 1.2 late in the cycle, there's no great harm done either. > What I don't want to be doing is creating artificial version bumps with > empty upgrade scripts in every release cycle --- that's make-work for > us, and make-work for our users too.
I would favor different release cycles for extensions than for the core product. It's a technical fact that a single extension source can and do support more than one major core version. And as soon as the code is maintained, next extension release would happen at next minor upgrade release. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
