Tom did most of the 8.4 stamping and I incremented the library minor
version numbers. I have updated the library bump wording in
RELEASE_CHANGES:
o Bump minor library versions, major if appropriate (see below)
I also updated this item description:
o update config.guess and
Sorry, please ignore me. I got start of beta confused with start of
development.
---
Bruce Momjian wrote:
Tom did most of the 8.4 stamping and I incremented the library minor
version numbers. I have updated the library
Stephen Frost [EMAIL PROTECTED] writes:
* Tom Lane ([EMAIL PROTECTED]) wrote:
Minor version bump is done unconditionally for each release cycle.
This isn't a *huge* deal, but I'm not sure it's actually appropriate.
We should bump the minor version when we actually add something new to
the
Alvaro Herrera wrote:
Bruce Momjian wrote:
Tom did most of the 8.4 stamping and I incremented the library minor
version numbers. I have updated the library bump wording in
RELEASE_CHANGES:
o Bump minor library versions, major if appropriate (see below)
I admit I am surprised
Bruce Momjian wrote:
Tom did most of the 8.4 stamping and I incremented the library minor
version numbers. I have updated the library bump wording in
RELEASE_CHANGES:
o Bump minor library versions, major if appropriate (see below)
I admit I am surprised by the library bump. We
Alvaro Herrera [EMAIL PROTECTED] writes:
I admit I am surprised by the library bump. We haven't done anything to
the libraries yet, so why bump the versions?
Minor version bump is done unconditionally for each release cycle.
Major version bump is as-needed (ABI break).
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I admit I am surprised by the library bump. We haven't done anything to
the libraries yet, so why bump the versions?
Minor version bump is done unconditionally for each release cycle.
Oh, I see. I will update RELEASE_CHANGES to
Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I admit I am surprised by the library bump. We haven't done anything to
the libraries yet, so why bump the versions?
Minor version bump is done unconditionally for each release cycle.
Oh, I see. I
* Tom Lane ([EMAIL PROTECTED]) wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I admit I am surprised by the library bump. We haven't done anything to
the libraries yet, so why bump the versions?
Minor version bump is done unconditionally for each release cycle.
This isn't a *huge* deal,
Stephen Frost wrote:
-- Start of PGP signed section.
* Tom Lane ([EMAIL PROTECTED]) wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I admit I am surprised by the library bump. We haven't done anything to
the libraries yet, so why bump the versions?
Minor version bump is done
Bruce Momjian [EMAIL PROTECTED] writes:
Stephen Frost wrote:
We should bump the minor version when we actually add something new to
the library (which is probably just about every time we do a major
version, but still).
The problem is the risk of forgetting during development. When we break
Bruce Momjian wrote:
Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I admit I am surprised by the library bump. We haven't done anything to
the libraries yet, so why bump the versions?
Minor version bump is done unconditionally for each release
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Stephen Frost wrote:
We should bump the minor version when we actually add something new to
the library (which is probably just about every time we do a major
version, but still).
The problem is the risk of forgetting during
13 matches
Mail list logo
