Re: Alpha releases: How to tag - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Alpha releases: How to tag
Date
Msg-id 4A76FB44.7030206@dunslane.net
Whole thread Raw
In response to Re: Alpha releases: How to tag  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Alpha releases: How to tag
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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;
> 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.
>
> I feel that making a branch is the way to go.  If we try to get away
> with a shortcut, we'll probably regret it.
>
>             
>   

Yes, if that's what we want then definitely branch. I guess the branch 
will (almost) only ever have exactly one commit on it.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CVS Head parser error?
Next
From: "Kevin Grittner"
Date:
Subject: Re: Review: Revise parallel pg_restore's scheduling heuristic