On Mon, 21 May 2007, Henri Yandell wrote:
Don't your jars contain the version number too?
Yeah, everything seems to :/
The most recent release types I've done are the type where you create
the exact release and put it in your ~login where it's voted on. I like
this because it makes the actua
On 5/21/07, Nick Burch <[EMAIL PROTECTED]> wrote:
Hi All
For the 3.0 release of POI, we followed the advice on voting on
artificats, the not the state of the tree. So, we used our ant script to
produce RC artificats, signed them, and placed them on people.apache.org
for review.
After the vote,
Nick Burch wrote:
> What do other people do about this for their releases, when voting on
> artificats? Do you do each build as if it was -FINAL (so that gets
> embeded into all the directory names etc), then rename the artificats
> for voting, or something else?
For Tomcat, every release candidat
For commons transaction I did exactly that.
Create/sign the RC as if it was the final release, but only put it on
temporary storage without notifying anyone external.
IMHO a RC is not meant to check for remaining bugs, but rather to see
if the distro looks ok, installs, etc.
That means the RC i
Hi All
For the 3.0 release of POI, we followed the advice on voting on
artificats, the not the state of the tree. So, we used our ant script to
produce RC artificats, signed them, and placed them on people.apache.org
for review.
After the vote, we renamed the files from -RC4- to -FINAL-, twe
