From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Alpha releases: How to tag |
Date: | 2009-08-03 15:17:24 |
Message-ID: | 20090803151724.GA25774@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 03, 2009 at 10:44:32AM -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > Does it need a version number change? Maybe just a tag (no branch)
> > is all that is required.
>
> I think that we do want the alpha releases to identify themselves as
> such. And we want a marker in CVS as to what state the alpha
> release corresponds to. Peter's label-and-undo approach seems like
> a kluge;
Right.
> and it doesn't scale to consider the possibility that we might want
> to re-release an alpha after fixing some particularly evil bug. A
> tag without a branch won't handle that either.
Is this a use case? I truly hope nobody will try using a beta, let
alone an alpha, in production. Do we need to provide for such a
possibility? I don't recall that we've ever back-patched a beta, or
even a release candidate.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-03 15:21:43 | Re: Review: Revise parallel pg_restore's scheduling heuristic |
Previous Message | Peter Eisentraut | 2009-08-03 15:15:53 | Re: Alpha releases: How to tag |