From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Contrib Versions |
Date: | 2011-05-12 22:09:24 |
Message-ID: | 11233.1305238164@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> Hackers,
> I don't suppose I could convince you to use dotted-decimal version numbers for the contrib extension versions, rather than numerics, could I? At this point, I think that would just mean changing them from 1.0 to 1.0.0.
> Why? Well, PGXN uses semantic versions, which have this format, so I'm biased that way when thinking about dependency resolution (which is coming in the the PGXN client). But the other reason is because I think it makes sense for all the versions in a project to be consistent, and the core versions have (mostly) always used this format.
I had somewhat intentionally not numbered them in the same format as the
main release numbers, because if we did that, people would expect them
to match the main release numbers.
I'm also still unwilling to make a core-code commitment to specific
requirements on extension version number format --- we've been around on
that multiple times already, and I don't think the arguments have
changed.
Having said that, I don't really care that much, except that it seems
a bit late in the release cycle to be changing this. People have
presumably already got installations that they hope to not have to
scratch and reload for 9.1 final.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-12 22:21:50 | Re: Unfriendly handling of pg_hba SSL options with SSL off |
Previous Message | Alexey Klyukin | 2011-05-12 22:09:16 | 'tuple concurrently updated' error for alter role ... set |