Hi,
On 1/17/07, Christoph Kiehl <[EMAIL PROTECTED]> wrote:
Jukka Zitting wrote:
> This is exactly what we do. The problem is that we can't use the -rcN
> builds for the final release vote since we don't want the -rcN suffix
> to be a part of the official release packages.
Ok, I see. Shouldn't it be possible to check out the revision you used to create
the 1.2.0-rcN release and release it again as 1.2.0? I'm not quite sure how the
release plugin handles this.
That would be optimal, i.e. vote on the last -rcN candidate and if the
vote passes, simply retag the release and remove the -rcN suffix to
create the official release packages. The show-stopper is that then
the released bits would not be exactly the same as the ones the PMC
voted on. :-(
BR,
Jukka Zitting
