You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Oliver Zeigermann <ol...@gmail.com> on 2006/07/24 13:26:27 UTC

[transaction] Preparing a release

Hi folks!

I have already uploaded the files for a 1.2 release candidate to

http://people.apache.org/~ozeigermann/tx-1.2rc1/

Not quite sure where to go from here.

Do we need a vote for the release candidate?

Where to put the files for the release candidate for public inspection?

Thanks in advance for any hints and cheers

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [transaction] Preparing a release

Posted by Niall Pemberton <ni...@gmail.com>.
On 7/24/06, Oliver Zeigermann <ol...@gmail.com> wrote:
> Hi folks!
>
> I have already uploaded the files for a 1.2 release candidate to
>
> http://people.apache.org/~ozeigermann/tx-1.2rc1/
>
> Not quite sure where to go from here.
>
> Do we need a vote for the release candidate?

Its your judgement call on how long you give people to review the
release candidate before calling a vote. I would typically give it at
least a week before calling a vote for a first RC. If you have to roll
subsequent RC then possibly a shorter timescale depending on the
amount of change and how trivial/non-trivial the changes are from the
previous RC - but again its your judgement call. If you state the
planned timescale and anyone doesn't like it, they can always shout.

> Where to put the files for the release candidate for public inspection?

Putting them in your personal space (as you have done) is the norm.

> Thanks in advance for any hints and cheers

I think the hard part is usually getting a RC to pass a vote -
satisfying the issues raised/nit picks. Once you get through that and
the vote has passed, its just a case of following the "cutting a
release" guidelines:

   http://jakarta.apache.org/commons/releases/release.html

I'll try to review rc1 soon and give you my feedback (hopefully not
much as I committed my transaction nit picks a week or two ago).

Niall

> Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [transaction] Preparing a release

Posted by Henri Yandell <fl...@gmail.com>.
On 7/25/06, Oliver Zeigermann <ol...@gmail.com> wrote:
> Hey, Henri!
>
> Thanks for the detailed feedback. Most of it should be fixed now. One
> more question: Where is the jar supposed to be? In the binary dist? It
> alreay is there! Or in the release directory? When to place the POM?

For the prepared rc, have the jar and the pom sitting in the rc
directory. Eventually it'll get put into the m1 ibiblio rsync
directory (/www/people.apache.org/repo/m1-ibiblio-rsync-repository/).

Both need to be hashed and signed.

Mostly it's a reminder to make sure you're thinking of deploying to
the m1 repo :)

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [transaction] Preparing a release

Posted by Oliver Zeigermann <ol...@gmail.com>.
Hey, Henri!

Thanks for the detailed feedback. Most of it should be fixed now. One
more question: Where is the jar supposed to be? In the binary dist? It
alreay is there! Or in the release directory? When to place the POM?

Oliver

2006/7/25, Henri Yandell <fl...@gmail.com>:
> On 7/24/06, Oliver Zeigermann <ol...@gmail.com> wrote:
> > Hi folks!
> >
> > I have already uploaded the files for a 1.2 release candidate to
> >
> > http://people.apache.org/~ozeigermann/tx-1.2rc1/
>
> Have you read the Releasing Components webpages?
>
> Few things to change:
>
> .MD5 to .md5
> .tgz to .tar.gz
> zips and tar.gz's should unzip to a directory with the same name as
> the archive (ie: it shouldn't make a mess when unpacked)
> include a jar for the Maven repository (and a .pom)
> gpg sign all files
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [transaction] Preparing a release

Posted by Henri Yandell <fl...@gmail.com>.
On 7/24/06, Oliver Zeigermann <ol...@gmail.com> wrote:
> Hi folks!
>
> I have already uploaded the files for a 1.2 release candidate to
>
> http://people.apache.org/~ozeigermann/tx-1.2rc1/

Have you read the Releasing Components webpages?

Few things to change:

.MD5 to .md5
.tgz to .tar.gz
zips and tar.gz's should unzip to a directory with the same name as
the archive (ie: it shouldn't make a mess when unpacked)
include a jar for the Maven repository (and a .pom)
gpg sign all files

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org