You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Sandy McArthur <sa...@apache.org> on 2006/03/20 03:32:07 UTC
[pool] ready for a 1.3 release?
I've preped Pool for a 1.3 to my satisfaction and uploaded the related files:
http://people.apache.org/~sandymac/pool/1.3-rc1/
http://people.apache.org/~sandymac/pool/1.3-rc1/site/
What's next? Do I start a vote or is that the job of a PMC member?
--
Sandy McArthur
"He who dares not offend cannot be honest."
- Thomas Paine
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [pool] ready for a 1.3 release?
Posted by Niall Pemberton <ni...@gmail.com>.
On 3/21/06, Sandy McArthur <sa...@apache.org> wrote:
> On 3/20/06, robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> > On Sun, 2006-03-19 at 21:32 -0500, Sandy McArthur wrote:
> > > I've preped Pool for a 1.3 to my satisfaction
> >
> > it's best to take a tag before each release candidate (just take a svn
> > copy from the current branch into the tags directory, named POOL_1_3_RC1
> > in this case). in the past we've occasionally needed to recut releases
> > and this is tricky (but not impossible) without tags.
> >
> > > and uploaded the related files:
> > > http://people.apache.org/~sandymac/pool/1.3-rc1/
> >
> > it's best for the source drop to unwrap to a different directory from
> > the binary release. traditionally commons-pool-1.3-rc1-src.tar.gz
> > should unpack to commons-pool-1.3-rc1-src (rather than
> > commons-pool-1.3-rc1). this makes it easier on user who want binary and
> > source.
>
> How do you express this with maven? I was able to figure out the other
> issues but I don't see how this option is configured.
Theres a couple of ways you can do this - Commons Math renames the
directory after the event (does a "move" in the "dist:build-scr"
pregoal in maven.xml).
Alternatively you could set the "maven.dist.src.assembly.dir" property
in your project.properties file:
maven.dist.src.assembly.dir=${maven.dist.assembly.dir}/src/${maven.final.name}-src
Niall
> > > http://people.apache.org/~sandymac/pool/1.3-rc1/site/
> >
> > looks good :)
> >
> > minor improvement: downloads are now host at
> > http://jakarta.apache.org/site/downloads/downloads_commons-pool.cgi.
> > download.xml needs to be updated. (don't forget to add a date for 1.3
> > when it's finally cut)
> >
> > please use lower case for the checksums suffix (AIUI the monitoring
> > scripts are case sensitive).
> >
> > signatures look fine to me. if you haven't uploaded your key to a public
> > key server on the academic network, please do so. (i use pgp.mit.edu.
> > henk has interesting material on signing and the apache web of trust at
> > http://people.apache.org/~henkp/)
> >
> > thanks for taking this on
> >
> > - robert
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
> --
> Sandy McArthur
>
> "He who dares not offend cannot be honest."
> - Thomas Paine
>
> ---------------------------------------------------------------------
> 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: [pool] ready for a 1.3 release?
Posted by Sandy McArthur <sa...@apache.org>.
On 3/20/06, robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> On Sun, 2006-03-19 at 21:32 -0500, Sandy McArthur wrote:
> > I've preped Pool for a 1.3 to my satisfaction
>
> it's best to take a tag before each release candidate (just take a svn
> copy from the current branch into the tags directory, named POOL_1_3_RC1
> in this case). in the past we've occasionally needed to recut releases
> and this is tricky (but not impossible) without tags.
>
> > and uploaded the related files:
> > http://people.apache.org/~sandymac/pool/1.3-rc1/
>
> it's best for the source drop to unwrap to a different directory from
> the binary release. traditionally commons-pool-1.3-rc1-src.tar.gz
> should unpack to commons-pool-1.3-rc1-src (rather than
> commons-pool-1.3-rc1). this makes it easier on user who want binary and
> source.
How do you express this with maven? I was able to figure out the other
issues but I don't see how this option is configured.
> > http://people.apache.org/~sandymac/pool/1.3-rc1/site/
>
> looks good :)
>
> minor improvement: downloads are now host at
> http://jakarta.apache.org/site/downloads/downloads_commons-pool.cgi.
> download.xml needs to be updated. (don't forget to add a date for 1.3
> when it's finally cut)
>
> please use lower case for the checksums suffix (AIUI the monitoring
> scripts are case sensitive).
>
> signatures look fine to me. if you haven't uploaded your key to a public
> key server on the academic network, please do so. (i use pgp.mit.edu.
> henk has interesting material on signing and the apache web of trust at
> http://people.apache.org/~henkp/)
>
> thanks for taking this on
>
> - robert
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
--
Sandy McArthur
"He who dares not offend cannot be honest."
- Thomas Paine
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [pool] ready for a 1.3 release?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sun, 2006-03-19 at 21:32 -0500, Sandy McArthur wrote:
> I've preped Pool for a 1.3 to my satisfaction
it's best to take a tag before each release candidate (just take a svn
copy from the current branch into the tags directory, named POOL_1_3_RC1
in this case). in the past we've occasionally needed to recut releases
and this is tricky (but not impossible) without tags.
> and uploaded the related files:
> http://people.apache.org/~sandymac/pool/1.3-rc1/
it's best for the source drop to unwrap to a different directory from
the binary release. traditionally commons-pool-1.3-rc1-src.tar.gz
should unpack to commons-pool-1.3-rc1-src (rather than
commons-pool-1.3-rc1). this makes it easier on user who want binary and
source.
> http://people.apache.org/~sandymac/pool/1.3-rc1/site/
looks good :)
minor improvement: downloads are now host at
http://jakarta.apache.org/site/downloads/downloads_commons-pool.cgi.
download.xml needs to be updated. (don't forget to add a date for 1.3
when it's finally cut)
please use lower case for the checksums suffix (AIUI the monitoring
scripts are case sensitive).
signatures look fine to me. if you haven't uploaded your key to a public
key server on the academic network, please do so. (i use pgp.mit.edu.
henk has interesting material on signing and the apache web of trust at
http://people.apache.org/~henkp/)
thanks for taking this on
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [pool] ready for a 1.3 release?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sun, 2006-03-19 at 21:32 -0500, Sandy McArthur wrote:
> I've preped Pool for a 1.3 to my satisfaction and uploaded the related files:
> http://people.apache.org/~sandymac/pool/1.3-rc1/
> http://people.apache.org/~sandymac/pool/1.3-rc1/site/
>
> What's next? Do I start a vote or is that the job of a PMC member?
anyone can start a VOTE :)
but only pmc'ers have votes that can bind the ASF legally.
a formal VOTE thread is required for a release.
if you start a VOTE, you should specify a duration (not less than a
week, say) and should tally the VOTEs on a [RESULT] post to the thread.
it's usually cleaner if you announce the first release candidate on list
first so that people involved with the component can check it. this
saves lots of VOTE threads one after another.
i usually start a release by nominating myself or someone else as
release manager and then preparing a release plan. these votes are done
by lazy consensus and no formal VOTE thread is necessary.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org