You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by James Carman <ja...@carmanconsulting.com> on 2008/02/20 00:31:56 UTC
[VOTE] Release Proxy 1.0 (from rc2)
All,
I have prepared a commons-proxy-1.0-rc2 release candidate. The
distribution files can be found at:
http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
and the site can be found at:
http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
The SVN tag used to create the release can be found at:
http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
All issues brought up thus far with the first release candidate have
been addressed. Again, this is my first release (including signing),
so please review thoroughly (not that you normally don't).
Thank you,
James Carman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/20/08, sebb <se...@gmail.com> wrote:
> No major problems, however there are some items that can be improved:
>
> Dependency Listings entry:
>
> >>>
> Commons Proxy
>
> Java library for dynamic proxying
>
> ../../../../../people.apache.org/www/commons.apache.org/proper/proxy/
> <<<
>
> Not sure where that originates, but it does not look right.
>
> Ideally there should be a Developer or Building page describing how to
> build the code.
>
By the way, there is a "Building Components" link on the navigation
pane on the left of every commons component site. However, it doesn't
have m2 instructions. Maybe it should. Then I wouldn't have to
create a proxy-specific one.
> It would be useful to have a text file in the source archive with
> basic build info as well.
>
> It would be good to mention the required Java version in the Release Notes.
>
>
> On 20/02/2008, Emmanuel Bourg <eb...@apache.org> wrote:
> > A few suggestions for the next release (don't hold 1.0 just for this if
> > you don't have the time) :
> >
> > - A tutorial with short code examples would be nice to get a quick taste
> > of the API. The overview page is not very sexy, I'm not a proxy guru and
> > I'm not sure to understand what I can achieve with the component.
> >
> > - package.html files are missing, the consequence is an almost blank
> > table when the Javadoc is opened
> >
> > - the javadoc for classes such as JavassistUtils is missing. Some
> > classes or interfaces with only one method have a javadoc at the class
> > level but not at the method level. I understand that the method comment
> > will most likely be redundant, but it's still useful for an IDE such as
> > IntelliJ that can display the method documentation in a popup window.
> >
> >
> > Emmanuel Bourg
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by sebb <se...@gmail.com>.
No major problems, however there are some items that can be improved:
Dependency Listings entry:
>>>
Commons Proxy
Java library for dynamic proxying
../../../../../people.apache.org/www/commons.apache.org/proper/proxy/
<<<
Not sure where that originates, but it does not look right.
Ideally there should be a Developer or Building page describing how to
build the code.
It would be useful to have a text file in the source archive with
basic build info as well.
It would be good to mention the required Java version in the Release Notes.
On 20/02/2008, Emmanuel Bourg <eb...@apache.org> wrote:
> A few suggestions for the next release (don't hold 1.0 just for this if
> you don't have the time) :
>
> - A tutorial with short code examples would be nice to get a quick taste
> of the API. The overview page is not very sexy, I'm not a proxy guru and
> I'm not sure to understand what I can achieve with the component.
>
> - package.html files are missing, the consequence is an almost blank
> table when the Javadoc is opened
>
> - the javadoc for classes such as JavassistUtils is missing. Some
> classes or interfaces with only one method have a javadoc at the class
> level but not at the method level. I understand that the method comment
> will most likely be redundant, but it's still useful for an IDE such as
> IntelliJ that can display the method documentation in a popup window.
>
>
> Emmanuel Bourg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Emmanuel Bourg <eb...@apache.org>.
A few suggestions for the next release (don't hold 1.0 just for this if
you don't have the time) :
- A tutorial with short code examples would be nice to get a quick taste
of the API. The overview page is not very sexy, I'm not a proxy guru and
I'm not sure to understand what I can achieve with the component.
- package.html files are missing, the consequence is an almost blank
table when the Javadoc is opened
- the javadoc for classes such as JavassistUtils is missing. Some
classes or interfaces with only one method have a javadoc at the class
level but not at the method level. I understand that the method comment
will most likely be redundant, but it's still useful for an IDE such as
IntelliJ that can display the method documentation in a popup window.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
Niall Pemberton wrote:
[snip]
> I don't think this works with the release plugin - which is another
> reason for doing it manually - one thing the plugin does is re-name
> the scm entries in the pom.xml to reflect the tag.
This is why Maven folks meanwhile use a stage plugin with a staging area.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Niall Pemberton <ni...@gmail.com>.
On Thu, Feb 21, 2008 at 5:57 PM, sebb <se...@gmail.com> wrote:
>
> On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> > On Thu, Feb 21, 2008 at 5:27 PM, sebb <se...@gmail.com> wrote:
> > >
> > > On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> > > > On Thu, Feb 21, 2008 at 3:18 PM, James Carman
> > > > <ja...@carmanconsulting.com> wrote:
> > > > > On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > > > > Yup, sorry about this - we changed process just over a year - I think
> > > > > > following this thread:
> > > > > > http://commons.markmail.org/message/vw3ckyjakjgbdlbu
> > > > > >
> > > > > > ...but no-one has go round to updating the docs. The other part of the
> > > > > > equation is maven2 - its only recently we started using m2 as the
> > > > > > primary build on some components - before that it was pretty much all
> > > > > > m1. The few recent m2 component releases have all be manual (rather
> > > > > > than using the m2 release plugin - I think JCI used that) - so I'm not
> > > > > > sure if we have a set procedure - but should document both options.
> > > > >
> > > > > Well, does anyone have explicit m2 instructions for doing these
> > > > > releases (using the profiles in commons-parent, I'd think)? I'm
> > > > > pretty familiar with m2 as far as day-to-day stuff (clean, test,
> > > > > install, etc.), but not for doing releases.
> > > >
> > > >
> > > > How about something like the following:
> > > >
> > > > 1) Tag "proxy-1.0-rc3" but with the version number set to "1.0"
> > > > 2) Check out the proxy-1.0-rc3
> > > > 3) Build the release artifacts - I think theres a couple of options here:
> > > >
> > > > 3.1) Run the following maven command:
> > > > mvn site javadoc:jar source:jar assembly:assembly
> > > >
> > > > This will create all the artifacts - jars and src and binary distros,
> > > > but then you need to create checksums and sign
> > > >
> > > > 3.2) Run the following maven command:
> > > > mvn -Prc -DcreateChecksum=true site install
> > > >
> > > > This should create all the artifacts installed in your local m2
> > > > repository, signed and checksums (note it also creates checksums for
> > > > signature files - I delete those)
> > > >
> > > > 4) Upload the artifacts to peopel.apache.org/~jcarman and call a vote on dev@
> > > >
> > > How about creating a temporary page on the Commons Wiki with this information?
> > >
> > > Once the process has been nailed down and tested, it should be moved
> > > to the formal website.
> >
> >
> > Yes, I'll try to find time to do this. The other option is to use the
> > maven release plugin - something along the lines:
> >
> > mvn -Prc release:prepare
> > mvn -Prc release:perform
> >
> > This has worked OK for me for releasing the poms - but I haven't tried
> > it on a component. The main thing I don't like about the release
> > plugin is that every time you do release:prepare, it does 3 commits -
> > which is alot of noise if you have several release candidates. Also
> > I'm not quite sure how we go from stage rc --> actual release. I guess
> > you have to tag and version as if it were the proper release - and
> > delete the tag if a RC fails.
> >
>
> Once the vote has passed, one can just copy the rc tag to the formal
> release tag.
I don't think this works with the release plugin - which is another
reason for doing it manually - one thing the plugin does is re-name
the scm entries in the pom.xml to reflect the tag.
> The RC tag should be kept (I guess any failed RC tags could be deleted).
>
> To help tie this together, it would be an idea to document the RC tag
> revision that is being voted on. If one wanted to be extra-careful, I
> guess one could also document the digests of the artifacts as well.
This is not necessary IMO.
Niall
> >
> > Niall
> >
> >
> > > > Niall
> > > >
> > > >
> > > > > >
> > > > > > Niall
> > > > > >
> > > > > >
> > > > > > > >
> > > > > > > > Oliver
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > >> Oliver
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> >
> > > > > > > > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > > > > > >> >> All,
> > > > > > > > >> >>
> > > > > > > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > > > > > >> >> distribution files can be found at:
> > > > > > > > >> >>
> > > > > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > > > > > > >> >>
> > > > > > > > >> >> and the site can be found at:
> > > > > > > > >> >>
> > > > > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > > > > > > >> >>
> > > > > > > > >> >> The SVN tag used to create the release can be found at:
> > > > > > > > >> >>
> > > > > > > > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > > > > > > >> >>
> > > > > > > > >> >> All issues brought up thus far with the first release candidate have
> > > > > > > > >> >> been addressed. Again, this is my first release (including signing),
> > > > > > > > >> >> so please review thoroughly (not that you normally don't).
> > > > > > > > >> >>
> > > > > > > > >> >> Thank you,
> > > > > > > > >> >>
> > > > > > > > >> >> James Carman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by sebb <se...@gmail.com>.
On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> On Thu, Feb 21, 2008 at 5:27 PM, sebb <se...@gmail.com> wrote:
> >
> > On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> > > On Thu, Feb 21, 2008 at 3:18 PM, James Carman
> > > <ja...@carmanconsulting.com> wrote:
> > > > On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > > > Yup, sorry about this - we changed process just over a year - I think
> > > > > following this thread:
> > > > > http://commons.markmail.org/message/vw3ckyjakjgbdlbu
> > > > >
> > > > > ...but no-one has go round to updating the docs. The other part of the
> > > > > equation is maven2 - its only recently we started using m2 as the
> > > > > primary build on some components - before that it was pretty much all
> > > > > m1. The few recent m2 component releases have all be manual (rather
> > > > > than using the m2 release plugin - I think JCI used that) - so I'm not
> > > > > sure if we have a set procedure - but should document both options.
> > > >
> > > > Well, does anyone have explicit m2 instructions for doing these
> > > > releases (using the profiles in commons-parent, I'd think)? I'm
> > > > pretty familiar with m2 as far as day-to-day stuff (clean, test,
> > > > install, etc.), but not for doing releases.
> > >
> > >
> > > How about something like the following:
> > >
> > > 1) Tag "proxy-1.0-rc3" but with the version number set to "1.0"
> > > 2) Check out the proxy-1.0-rc3
> > > 3) Build the release artifacts - I think theres a couple of options here:
> > >
> > > 3.1) Run the following maven command:
> > > mvn site javadoc:jar source:jar assembly:assembly
> > >
> > > This will create all the artifacts - jars and src and binary distros,
> > > but then you need to create checksums and sign
> > >
> > > 3.2) Run the following maven command:
> > > mvn -Prc -DcreateChecksum=true site install
> > >
> > > This should create all the artifacts installed in your local m2
> > > repository, signed and checksums (note it also creates checksums for
> > > signature files - I delete those)
> > >
> > > 4) Upload the artifacts to peopel.apache.org/~jcarman and call a vote on dev@
> > >
> > How about creating a temporary page on the Commons Wiki with this information?
> >
> > Once the process has been nailed down and tested, it should be moved
> > to the formal website.
>
>
> Yes, I'll try to find time to do this. The other option is to use the
> maven release plugin - something along the lines:
>
> mvn -Prc release:prepare
> mvn -Prc release:perform
>
> This has worked OK for me for releasing the poms - but I haven't tried
> it on a component. The main thing I don't like about the release
> plugin is that every time you do release:prepare, it does 3 commits -
> which is alot of noise if you have several release candidates. Also
> I'm not quite sure how we go from stage rc --> actual release. I guess
> you have to tag and version as if it were the proper release - and
> delete the tag if a RC fails.
>
Once the vote has passed, one can just copy the rc tag to the formal
release tag.
The RC tag should be kept (I guess any failed RC tags could be deleted).
To help tie this together, it would be an idea to document the RC tag
revision that is being voted on. If one wanted to be extra-careful, I
guess one could also document the digests of the artifacts as well.
>
> Niall
>
>
> > > Niall
> > >
> > >
> > > > >
> > > > > Niall
> > > > >
> > > > >
> > > > > > >
> > > > > > > Oliver
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >> Oliver
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> >
> > > > > > > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > > > > >> >> All,
> > > > > > > >> >>
> > > > > > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > > > > >> >> distribution files can be found at:
> > > > > > > >> >>
> > > > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > > > > > >> >>
> > > > > > > >> >> and the site can be found at:
> > > > > > > >> >>
> > > > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > > > > > >> >>
> > > > > > > >> >> The SVN tag used to create the release can be found at:
> > > > > > > >> >>
> > > > > > > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > > > > > >> >>
> > > > > > > >> >> All issues brought up thus far with the first release candidate have
> > > > > > > >> >> been addressed. Again, this is my first release (including signing),
> > > > > > > >> >> so please review thoroughly (not that you normally don't).
> > > > > > > >> >>
> > > > > > > >> >> Thank you,
> > > > > > > >> >>
> > > > > > > >> >> James Carman
> > >
> >
> >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by simon <si...@chello.at>.
On Thu, 2008-02-21 at 17:43 +0000, Niall Pemberton wrote:
> On Thu, Feb 21, 2008 at 5:27 PM, sebb <se...@gmail.com> wrote:
> >
> > On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> > > On Thu, Feb 21, 2008 at 3:18 PM, James Carman
> > > <ja...@carmanconsulting.com> wrote:
> > > > On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > > > Yup, sorry about this - we changed process just over a year - I think
> > > > > following this thread:
> > > > > http://commons.markmail.org/message/vw3ckyjakjgbdlbu
> > > > >
> > > > > ...but no-one has go round to updating the docs. The other part of the
> > > > > equation is maven2 - its only recently we started using m2 as the
> > > > > primary build on some components - before that it was pretty much all
> > > > > m1. The few recent m2 component releases have all be manual (rather
> > > > > than using the m2 release plugin - I think JCI used that) - so I'm not
> > > > > sure if we have a set procedure - but should document both options.
> > > >
> > > > Well, does anyone have explicit m2 instructions for doing these
> > > > releases (using the profiles in commons-parent, I'd think)? I'm
> > > > pretty familiar with m2 as far as day-to-day stuff (clean, test,
> > > > install, etc.), but not for doing releases.
> > >
> > >
> > > How about something like the following:
> > >
> > > 1) Tag "proxy-1.0-rc3" but with the version number set to "1.0"
> > > 2) Check out the proxy-1.0-rc3
> > > 3) Build the release artifacts - I think theres a couple of options here:
> > >
> > > 3.1) Run the following maven command:
> > > mvn site javadoc:jar source:jar assembly:assembly
> > >
> > > This will create all the artifacts - jars and src and binary distros,
> > > but then you need to create checksums and sign
> > >
> > > 3.2) Run the following maven command:
> > > mvn -Prc -DcreateChecksum=true site install
> > >
> > > This should create all the artifacts installed in your local m2
> > > repository, signed and checksums (note it also creates checksums for
> > > signature files - I delete those)
> > >
> > > 4) Upload the artifacts to peopel.apache.org/~jcarman and call a vote on dev@
> > >
> > How about creating a temporary page on the Commons Wiki with this information?
> >
> > Once the process has been nailed down and tested, it should be moved
> > to the formal website.
>
> Yes, I'll try to find time to do this. The other option is to use the
> maven release plugin - something along the lines:
>
> mvn -Prc release:prepare
> mvn -Prc release:perform
>
> This has worked OK for me for releasing the poms - but I haven't tried
> it on a component. The main thing I don't like about the release
> plugin is that every time you do release:prepare, it does 3 commits -
> which is alot of noise if you have several release candidates. Also
> I'm not quite sure how we go from stage rc --> actual release. I guess
> you have to tag and version as if it were the proper release - and
> delete the tag if a RC fails.
Yeah, the release plugin is "sub-optimal". It just occurred to me
recently that it probably does this in order to be able to support CVS
etc which cannot so easily branch, fix branch, tag. Instead it does "fix
trunk", tag, "refix trunk".
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Niall Pemberton <ni...@gmail.com>.
On Thu, Feb 21, 2008 at 5:27 PM, sebb <se...@gmail.com> wrote:
>
> On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> > On Thu, Feb 21, 2008 at 3:18 PM, James Carman
> > <ja...@carmanconsulting.com> wrote:
> > > On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > > Yup, sorry about this - we changed process just over a year - I think
> > > > following this thread:
> > > > http://commons.markmail.org/message/vw3ckyjakjgbdlbu
> > > >
> > > > ...but no-one has go round to updating the docs. The other part of the
> > > > equation is maven2 - its only recently we started using m2 as the
> > > > primary build on some components - before that it was pretty much all
> > > > m1. The few recent m2 component releases have all be manual (rather
> > > > than using the m2 release plugin - I think JCI used that) - so I'm not
> > > > sure if we have a set procedure - but should document both options.
> > >
> > > Well, does anyone have explicit m2 instructions for doing these
> > > releases (using the profiles in commons-parent, I'd think)? I'm
> > > pretty familiar with m2 as far as day-to-day stuff (clean, test,
> > > install, etc.), but not for doing releases.
> >
> >
> > How about something like the following:
> >
> > 1) Tag "proxy-1.0-rc3" but with the version number set to "1.0"
> > 2) Check out the proxy-1.0-rc3
> > 3) Build the release artifacts - I think theres a couple of options here:
> >
> > 3.1) Run the following maven command:
> > mvn site javadoc:jar source:jar assembly:assembly
> >
> > This will create all the artifacts - jars and src and binary distros,
> > but then you need to create checksums and sign
> >
> > 3.2) Run the following maven command:
> > mvn -Prc -DcreateChecksum=true site install
> >
> > This should create all the artifacts installed in your local m2
> > repository, signed and checksums (note it also creates checksums for
> > signature files - I delete those)
> >
> > 4) Upload the artifacts to peopel.apache.org/~jcarman and call a vote on dev@
> >
> How about creating a temporary page on the Commons Wiki with this information?
>
> Once the process has been nailed down and tested, it should be moved
> to the formal website.
Yes, I'll try to find time to do this. The other option is to use the
maven release plugin - something along the lines:
mvn -Prc release:prepare
mvn -Prc release:perform
This has worked OK for me for releasing the poms - but I haven't tried
it on a component. The main thing I don't like about the release
plugin is that every time you do release:prepare, it does 3 commits -
which is alot of noise if you have several release candidates. Also
I'm not quite sure how we go from stage rc --> actual release. I guess
you have to tag and version as if it were the proper release - and
delete the tag if a RC fails.
Niall
> > Niall
> >
> >
> > > >
> > > > Niall
> > > >
> > > >
> > > > > >
> > > > > > Oliver
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >> Oliver
> > > > > > >>
> > > > > > >>
> > > > > > >> >
> > > > > > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > > > >> >> All,
> > > > > > >> >>
> > > > > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > > > >> >> distribution files can be found at:
> > > > > > >> >>
> > > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > > > > >> >>
> > > > > > >> >> and the site can be found at:
> > > > > > >> >>
> > > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > > > > >> >>
> > > > > > >> >> The SVN tag used to create the release can be found at:
> > > > > > >> >>
> > > > > > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > > > > >> >>
> > > > > > >> >> All issues brought up thus far with the first release candidate have
> > > > > > >> >> been addressed. Again, this is my first release (including signing),
> > > > > > >> >> so please review thoroughly (not that you normally don't).
> > > > > > >> >>
> > > > > > >> >> Thank you,
> > > > > > >> >>
> > > > > > >> >> James Carman
> >
>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by sebb <se...@gmail.com>.
On 21/02/2008, James Carman <ja...@carmanconsulting.com> wrote:
> On 2/21/08, sebb <se...@gmail.com> wrote:
> > How about creating a temporary page on the Commons Wiki with this information?
> >
> > Once the process has been nailed down and tested, it should be moved
> > to the formal website.
> >
>
>
> I like this idea! I can try to update it with anything I run into as
> I go through doing the proxy 1.0 release.
>
I've made a start with:
http://wiki.apache.org/commons/CreatingReleases
It's deliberately not yet linked from the front page.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/21/08, sebb <se...@gmail.com> wrote:
> How about creating a temporary page on the Commons Wiki with this information?
>
> Once the process has been nailed down and tested, it should be moved
> to the formal website.
>
I like this idea! I can try to update it with anything I run into as
I go through doing the proxy 1.0 release.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by sebb <se...@gmail.com>.
On 21/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
> On Thu, Feb 21, 2008 at 3:18 PM, James Carman
> <ja...@carmanconsulting.com> wrote:
> > On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > Yup, sorry about this - we changed process just over a year - I think
> > > following this thread:
> > > http://commons.markmail.org/message/vw3ckyjakjgbdlbu
> > >
> > > ...but no-one has go round to updating the docs. The other part of the
> > > equation is maven2 - its only recently we started using m2 as the
> > > primary build on some components - before that it was pretty much all
> > > m1. The few recent m2 component releases have all be manual (rather
> > > than using the m2 release plugin - I think JCI used that) - so I'm not
> > > sure if we have a set procedure - but should document both options.
> >
> > Well, does anyone have explicit m2 instructions for doing these
> > releases (using the profiles in commons-parent, I'd think)? I'm
> > pretty familiar with m2 as far as day-to-day stuff (clean, test,
> > install, etc.), but not for doing releases.
>
>
> How about something like the following:
>
> 1) Tag "proxy-1.0-rc3" but with the version number set to "1.0"
> 2) Check out the proxy-1.0-rc3
> 3) Build the release artifacts - I think theres a couple of options here:
>
> 3.1) Run the following maven command:
> mvn site javadoc:jar source:jar assembly:assembly
>
> This will create all the artifacts - jars and src and binary distros,
> but then you need to create checksums and sign
>
> 3.2) Run the following maven command:
> mvn -Prc -DcreateChecksum=true site install
>
> This should create all the artifacts installed in your local m2
> repository, signed and checksums (note it also creates checksums for
> signature files - I delete those)
>
> 4) Upload the artifacts to peopel.apache.org/~jcarman and call a vote on dev@
>
>
How about creating a temporary page on the Commons Wiki with this information?
Once the process has been nailed down and tested, it should be moved
to the formal website.
> Niall
>
>
> > >
> > > Niall
> > >
> > >
> > > > >
> > > > > Oliver
> > > > >
> > > > >
> > > > > >
> > > > > >> Oliver
> > > > > >>
> > > > > >>
> > > > > >> >
> > > > > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > > >> >> All,
> > > > > >> >>
> > > > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > > >> >> distribution files can be found at:
> > > > > >> >>
> > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > > > >> >>
> > > > > >> >> and the site can be found at:
> > > > > >> >>
> > > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > > > >> >>
> > > > > >> >> The SVN tag used to create the release can be found at:
> > > > > >> >>
> > > > > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > > > >> >>
> > > > > >> >> All issues brought up thus far with the first release candidate have
> > > > > >> >> been addressed. Again, this is my first release (including signing),
> > > > > >> >> so please review thoroughly (not that you normally don't).
> > > > > >> >>
> > > > > >> >> Thank you,
> > > > > >> >>
> > > > > >> >> James Carman
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Niall Pemberton <ni...@gmail.com>.
On Thu, Feb 21, 2008 at 3:18 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> > Yup, sorry about this - we changed process just over a year - I think
> > following this thread:
> > http://commons.markmail.org/message/vw3ckyjakjgbdlbu
> >
> > ...but no-one has go round to updating the docs. The other part of the
> > equation is maven2 - its only recently we started using m2 as the
> > primary build on some components - before that it was pretty much all
> > m1. The few recent m2 component releases have all be manual (rather
> > than using the m2 release plugin - I think JCI used that) - so I'm not
> > sure if we have a set procedure - but should document both options.
>
> Well, does anyone have explicit m2 instructions for doing these
> releases (using the profiles in commons-parent, I'd think)? I'm
> pretty familiar with m2 as far as day-to-day stuff (clean, test,
> install, etc.), but not for doing releases.
How about something like the following:
1) Tag "proxy-1.0-rc3" but with the version number set to "1.0"
2) Check out the proxy-1.0-rc3
3) Build the release artifacts - I think theres a couple of options here:
3.1) Run the following maven command:
mvn site javadoc:jar source:jar assembly:assembly
This will create all the artifacts - jars and src and binary distros,
but then you need to create checksums and sign
3.2) Run the following maven command:
mvn -Prc -DcreateChecksum=true site install
This should create all the artifacts installed in your local m2
repository, signed and checksums (note it also creates checksums for
signature files - I delete those)
4) Upload the artifacts to peopel.apache.org/~jcarman and call a vote on dev@
Niall
> >
> > Niall
> >
> >
> > > >
> > > > Oliver
> > > >
> > > >
> > > > >
> > > > >> Oliver
> > > > >>
> > > > >>
> > > > >> >
> > > > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > >> >> All,
> > > > >> >>
> > > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > >> >> distribution files can be found at:
> > > > >> >>
> > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > > >> >>
> > > > >> >> and the site can be found at:
> > > > >> >>
> > > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > > >> >>
> > > > >> >> The SVN tag used to create the release can be found at:
> > > > >> >>
> > > > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > > >> >>
> > > > >> >> All issues brought up thus far with the first release candidate have
> > > > >> >> been addressed. Again, this is my first release (including signing),
> > > > >> >> so please review thoroughly (not that you normally don't).
> > > > >> >>
> > > > >> >> Thank you,
> > > > >> >>
> > > > >> >> James Carman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/20/08, Niall Pemberton <ni...@gmail.com> wrote:
> Yup, sorry about this - we changed process just over a year - I think
> following this thread:
> http://commons.markmail.org/message/vw3ckyjakjgbdlbu
>
> ...but no-one has go round to updating the docs. The other part of the
> equation is maven2 - its only recently we started using m2 as the
> primary build on some components - before that it was pretty much all
> m1. The few recent m2 component releases have all be manual (rather
> than using the m2 release plugin - I think JCI used that) - so I'm not
> sure if we have a set procedure - but should document both options.
Well, does anyone have explicit m2 instructions for doing these
releases (using the profiles in commons-parent, I'd think)? I'm
pretty familiar with m2 as far as day-to-day stuff (clean, test,
install, etc.), but not for doing releases.
>
>
> Niall
>
>
> > >
> > > Oliver
> > >
> > >
> > > >
> > > >> Oliver
> > > >>
> > > >>
> > > >> >
> > > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > >> >> All,
> > > >> >>
> > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > >> >> distribution files can be found at:
> > > >> >>
> > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > >> >>
> > > >> >> and the site can be found at:
> > > >> >>
> > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > >> >>
> > > >> >> The SVN tag used to create the release can be found at:
> > > >> >>
> > > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > >> >>
> > > >> >> All issues brought up thus far with the first release candidate have
> > > >> >> been addressed. Again, this is my first release (including signing),
> > > >> >> so please review thoroughly (not that you normally don't).
> > > >> >>
> > > >> >> Thank you,
> > > >> >>
> > > >> >> James Carman
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Niall Pemberton <ni...@gmail.com>.
On Wed, Feb 20, 2008 at 10:03 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> On 2/20/08, Oliver Heger <ol...@oliver-heger.de> wrote:
> >
> >
>
> > You are right, the release instructions seem to be outdated in this area.
> >
> > It has become common practice to cut release candidates, tag them as
> > such in subversion, but set the version numbers to the actual release
> > version. (Typically you set the version, e.g. 1.0, in the pom, create
> > the distributions and the subversion tag for the rc, and then roll-back
> > the version number to the snapshot version, for the case that the vote
> > fails.)
> >
> > So these artifacts look exactly like release artifacts. (To avoid
> > confusion, they are not announced in the public, but only on the dev list.)
> >
> > Then if the vote passes, these artifacts can directly be deployed to the
> > maven repo, and the tag for the rc can be copied to the release tag.
> > Otherwise a new iteration is necessary.
> >
>
> So, should we create a JIRA somewhere or somehow capture the fact that
> the release directions need to be edited by someone? I would also
> recommend we put in there all of the nice mvn commands to get this
> working (mvn -Prc site assembly:assembly, for instance).
Yup, sorry about this - we changed process just over a year - I think
following this thread:
http://commons.markmail.org/message/vw3ckyjakjgbdlbu
...but no-one has go round to updating the docs. The other part of the
equation is maven2 - its only recently we started using m2 as the
primary build on some components - before that it was pretty much all
m1. The few recent m2 component releases have all be manual (rather
than using the m2 release plugin - I think JCI used that) - so I'm not
sure if we have a set procedure - but should document both options.
Niall
> >
> > Oliver
> >
> >
> > >
> > >> Oliver
> > >>
> > >>
> > >> >
> > >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > >> >> All,
> > >> >>
> > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > >> >> distribution files can be found at:
> > >> >>
> > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > >> >>
> > >> >> and the site can be found at:
> > >> >>
> > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > >> >>
> > >> >> The SVN tag used to create the release can be found at:
> > >> >>
> > >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > >> >>
> > >> >> All issues brought up thus far with the first release candidate have
> > >> >> been addressed. Again, this is my first release (including signing),
> > >> >> so please review thoroughly (not that you normally don't).
> > >> >>
> > >> >> Thank you,
> > >> >>
> > >> >> James Carman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/20/08, Oliver Heger <ol...@oliver-heger.de> wrote:
>
>
> You are right, the release instructions seem to be outdated in this area.
>
> It has become common practice to cut release candidates, tag them as
> such in subversion, but set the version numbers to the actual release
> version. (Typically you set the version, e.g. 1.0, in the pom, create
> the distributions and the subversion tag for the rc, and then roll-back
> the version number to the snapshot version, for the case that the vote
> fails.)
>
> So these artifacts look exactly like release artifacts. (To avoid
> confusion, they are not announced in the public, but only on the dev list.)
>
> Then if the vote passes, these artifacts can directly be deployed to the
> maven repo, and the tag for the rc can be copied to the release tag.
> Otherwise a new iteration is necessary.
>
So, should we create a JIRA somewhere or somehow capture the fact that
the release directions need to be edited by someone? I would also
recommend we put in there all of the nice mvn commands to get this
working (mvn -Prc site assembly:assembly, for instance).
>
> Oliver
>
>
> >
> >> Oliver
> >>
> >>
> >> >
> >> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> >> >> All,
> >> >>
> >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> >> >> distribution files can be found at:
> >> >>
> >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> >> >>
> >> >> and the site can be found at:
> >> >>
> >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> >> >>
> >> >> The SVN tag used to create the release can be found at:
> >> >>
> >> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> >> >>
> >> >> All issues brought up thus far with the first release candidate have
> >> >> been addressed. Again, this is my first release (including signing),
> >> >> so please review thoroughly (not that you normally don't).
> >> >>
> >> >> Thank you,
> >> >>
> >> >> James Carman
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> > For additional commands, e-mail: dev-help@commons.apache.org
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Oliver Heger <ol...@oliver-heger.de>.
James Carman schrieb:
> On 2/20/08, Oliver Heger <ol...@oliver-heger.de> wrote:
>> Niall Pemberton schrieb:
>>
>>> I'm +0 on this release because I like to review the actual artifacts
>> > that are going to be distributed. The distros IMO meet ASF release
>> > requirements but if I run command "mvn -Prc site assembly:assembly"
>> > then the binary distro created also includes the javadocs and also
>> > -sources.jar and -javadoc.jar. Which kind of makes the argument for
>> > reviewing actual artifacts.
>> >
>> > Niall
>>
>>
>> Same for me. The artifacts look good. Looking forward for the final
>> distributions.
>>
>
> So, are you guys saying that you want to vote on the actual files that
> will be released? While I agree that is a good way to do it, that
> doesn't go along with the directions for preparing/cutting a release
> that we have on our site. According to the directions, I am to cut
> the release candidates (with the -rc* version numbers in the pom)
> until I get an affirmative vote (I believe three +1s are required and
> right now I have one if I'm allowed to count mine). Then, I cut the
> actual release (again by changing the pom.xml file to add in the real
> version number for the release) and checksum, sign, and deploy it.
> There is no vote again according to the directions.
>
> So, do you guys want me to cut the actual release and let you vote on
> that? Is that what you mean by "looking forward for the final
> distributions"? If this is the case, shouldn't we update the
> directions to let folks know? Maybe we should do [DISCUSS] threads on
> the candidates until folks feel comfortable with them and then do a
> [VOTE] thread? If something shows up after the discussions that
> someone isn't comfortable with, we can always go back to cutting
> candidates until the kinks are ironed out.
You are right, the release instructions seem to be outdated in this area.
It has become common practice to cut release candidates, tag them as
such in subversion, but set the version numbers to the actual release
version. (Typically you set the version, e.g. 1.0, in the pom, create
the distributions and the subversion tag for the rc, and then roll-back
the version number to the snapshot version, for the case that the vote
fails.)
So these artifacts look exactly like release artifacts. (To avoid
confusion, they are not announced in the public, but only on the dev list.)
Then if the vote passes, these artifacts can directly be deployed to the
maven repo, and the tag for the rc can be copied to the release tag.
Otherwise a new iteration is necessary.
Oliver
>
>> Oliver
>>
>>
>> >
>> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
>> >> All,
>> >>
>> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
>> >> distribution files can be found at:
>> >>
>> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
>> >>
>> >> and the site can be found at:
>> >>
>> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
>> >>
>> >> The SVN tag used to create the release can be found at:
>> >>
>> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
>> >>
>> >> All issues brought up thus far with the first release candidate have
>> >> been addressed. Again, this is my first release (including signing),
>> >> so please review thoroughly (not that you normally don't).
>> >>
>> >> Thank you,
>> >>
>> >> James Carman
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/20/08, Oliver Heger <ol...@oliver-heger.de> wrote:
> Niall Pemberton schrieb:
>
> > I'm +0 on this release because I like to review the actual artifacts
> > that are going to be distributed. The distros IMO meet ASF release
> > requirements but if I run command "mvn -Prc site assembly:assembly"
> > then the binary distro created also includes the javadocs and also
> > -sources.jar and -javadoc.jar. Which kind of makes the argument for
> > reviewing actual artifacts.
> >
> > Niall
>
>
> Same for me. The artifacts look good. Looking forward for the final
> distributions.
>
So, are you guys saying that you want to vote on the actual files that
will be released? While I agree that is a good way to do it, that
doesn't go along with the directions for preparing/cutting a release
that we have on our site. According to the directions, I am to cut
the release candidates (with the -rc* version numbers in the pom)
until I get an affirmative vote (I believe three +1s are required and
right now I have one if I'm allowed to count mine). Then, I cut the
actual release (again by changing the pom.xml file to add in the real
version number for the release) and checksum, sign, and deploy it.
There is no vote again according to the directions.
So, do you guys want me to cut the actual release and let you vote on
that? Is that what you mean by "looking forward for the final
distributions"? If this is the case, shouldn't we update the
directions to let folks know? Maybe we should do [DISCUSS] threads on
the candidates until folks feel comfortable with them and then do a
[VOTE] thread? If something shows up after the discussions that
someone isn't comfortable with, we can always go back to cutting
candidates until the kinks are ironed out.
>
> Oliver
>
>
> >
> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> >> All,
> >>
> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> >> distribution files can be found at:
> >>
> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> >>
> >> and the site can be found at:
> >>
> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> >>
> >> The SVN tag used to create the release can be found at:
> >>
> >> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> >>
> >> All issues brought up thus far with the first release candidate have
> >> been addressed. Again, this is my first release (including signing),
> >> so please review thoroughly (not that you normally don't).
> >>
> >> Thank you,
> >>
> >> James Carman
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Oliver Heger <ol...@oliver-heger.de>.
Niall Pemberton schrieb:
> I'm +0 on this release because I like to review the actual artifacts
> that are going to be distributed. The distros IMO meet ASF release
> requirements but if I run command "mvn -Prc site assembly:assembly"
> then the binary distro created also includes the javadocs and also
> -sources.jar and -javadoc.jar. Which kind of makes the argument for
> reviewing actual artifacts.
>
> Niall
Same for me. The artifacts look good. Looking forward for the final
distributions.
Oliver
>
> On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
>> All,
>>
>> I have prepared a commons-proxy-1.0-rc2 release candidate. The
>> distribution files can be found at:
>>
>> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
>>
>> and the site can be found at:
>>
>> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
>>
>> The SVN tag used to create the release can be found at:
>>
>> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
>>
>> All issues brought up thus far with the first release candidate have
>> been addressed. Again, this is my first release (including signing),
>> so please review thoroughly (not that you normally don't).
>>
>> Thank you,
>>
>> James Carman
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/19/08, Niall Pemberton <ni...@gmail.com> wrote:
> On Feb 20, 2008 4:32 AM, James Carman <ja...@carmanconsulting.com> wrote:
> > On 2/19/08, James Carman <ja...@carmanconsulting.com> wrote:
> > > On 2/19/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > > I'm +0 on this release because I like to review the actual artifacts
> > > > that are going to be distributed. The distros IMO meet ASF release
> > > > requirements but if I run command "mvn -Prc site assembly:assembly"
> > > > then the binary distro created also includes the javadocs and also
> > > > -sources.jar and -javadoc.jar. Which kind of makes the argument for
> > > > reviewing actual artifacts.
> > >
> > > Is there something in the pom that shouldn't be there? I don't think
> > > there's anything too crazy in the pom that should cause it to be
> > > generating weird artifacts. Is it something in the parent pom?
>
> No nothing weird - just pointing out that you can get some additional
> stuff that is nice-to-have that was missing from your rc
>
Ahhhh, I see. So, should I re-cut the rc2 using the correct
parameters? Or, should I generate an rc3? If I'm not changing
anything and I'm really just running a different command, it would
seem weird to have to create a whole new tag/version.
> > Are we supposed to be using the "rc" (I take it that means release
> > candidate) profile when building?
>
> Yes - if you do it generates the javadoc and sources jars for you -
> which are nice-to-have.
>
> > That wasn't in the instructions.
> > The distros that I built were done using mvn assembly:assembly and
> > site without the profile activated.
>
> The "bin" assembly descriptor includes the apidocs folder, but you
> need the site generated first - so specifying "site" goal before
> "assembly:assembly" achieves that.
>
> Then, I hand-signed the artifacts
> > and generated the md5 checksums. I guess I could have used the maven
> > plugin, huh? :)
I am getting a NullPointerException on the gpg:sign goal. I can run
the gpg command by itself and sign stuff. I just can't get it working
using the maven plugin.
> >
> > >
> > > >
> > > > Niall
> > > >
> > > > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > > All,
> > > > >
> > > > > I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > > distribution files can be found at:
> > > > >
> > > > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > > >
> > > > > and the site can be found at:
> > > > >
> > > > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > > >
> > > > > The SVN tag used to create the release can be found at:
> > > > >
> > > > > http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > > >
> > > > > All issues brought up thus far with the first release candidate have
> > > > > been addressed. Again, this is my first release (including signing),
> > > > > so please review thoroughly (not that you normally don't).
> > > > >
> > > > > Thank you,
> > > > >
> > > > > James Carman
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Niall Pemberton <ni...@gmail.com>.
On Feb 20, 2008 4:32 AM, James Carman <ja...@carmanconsulting.com> wrote:
> On 2/19/08, James Carman <ja...@carmanconsulting.com> wrote:
> > On 2/19/08, Niall Pemberton <ni...@gmail.com> wrote:
> > > I'm +0 on this release because I like to review the actual artifacts
> > > that are going to be distributed. The distros IMO meet ASF release
> > > requirements but if I run command "mvn -Prc site assembly:assembly"
> > > then the binary distro created also includes the javadocs and also
> > > -sources.jar and -javadoc.jar. Which kind of makes the argument for
> > > reviewing actual artifacts.
> >
> > Is there something in the pom that shouldn't be there? I don't think
> > there's anything too crazy in the pom that should cause it to be
> > generating weird artifacts. Is it something in the parent pom?
No nothing weird - just pointing out that you can get some additional
stuff that is nice-to-have that was missing from your rc
> Are we supposed to be using the "rc" (I take it that means release
> candidate) profile when building?
Yes - if you do it generates the javadoc and sources jars for you -
which are nice-to-have.
> That wasn't in the instructions.
> The distros that I built were done using mvn assembly:assembly and
> site without the profile activated.
The "bin" assembly descriptor includes the apidocs folder, but you
need the site generated first - so specifying "site" goal before
"assembly:assembly" achieves that.
Then, I hand-signed the artifacts
> and generated the md5 checksums. I guess I could have used the maven
> plugin, huh? :)
>
> >
> > >
> > > Niall
> > >
> > > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > > All,
> > > >
> > > > I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > > distribution files can be found at:
> > > >
> > > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > > >
> > > > and the site can be found at:
> > > >
> > > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > > >
> > > > The SVN tag used to create the release can be found at:
> > > >
> > > > http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > > >
> > > > All issues brought up thus far with the first release candidate have
> > > > been addressed. Again, this is my first release (including signing),
> > > > so please review thoroughly (not that you normally don't).
> > > >
> > > > Thank you,
> > > >
> > > > James Carman
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/19/08, James Carman <ja...@carmanconsulting.com> wrote:
> On 2/19/08, Niall Pemberton <ni...@gmail.com> wrote:
> > I'm +0 on this release because I like to review the actual artifacts
> > that are going to be distributed. The distros IMO meet ASF release
> > requirements but if I run command "mvn -Prc site assembly:assembly"
> > then the binary distro created also includes the javadocs and also
> > -sources.jar and -javadoc.jar. Which kind of makes the argument for
> > reviewing actual artifacts.
>
> Is there something in the pom that shouldn't be there? I don't think
> there's anything too crazy in the pom that should cause it to be
> generating weird artifacts. Is it something in the parent pom?
Are we supposed to be using the "rc" (I take it that means release
candidate) profile when building? That wasn't in the instructions.
The distros that I built were done using mvn assembly:assembly and
site without the profile activated. Then, I hand-signed the artifacts
and generated the md5 checksums. I guess I could have used the maven
plugin, huh? :)
>
> >
> > Niall
> >
> > On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > > All,
> > >
> > > I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > > distribution files can be found at:
> > >
> > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> > >
> > > and the site can be found at:
> > >
> > > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> > >
> > > The SVN tag used to create the release can be found at:
> > >
> > > http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> > >
> > > All issues brought up thus far with the first release candidate have
> > > been addressed. Again, this is my first release (including signing),
> > > so please review thoroughly (not that you normally don't).
> > >
> > > Thank you,
> > >
> > > James Carman
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/19/08, Niall Pemberton <ni...@gmail.com> wrote:
> I'm +0 on this release because I like to review the actual artifacts
> that are going to be distributed. The distros IMO meet ASF release
> requirements but if I run command "mvn -Prc site assembly:assembly"
> then the binary distro created also includes the javadocs and also
> -sources.jar and -javadoc.jar. Which kind of makes the argument for
> reviewing actual artifacts.
Is there something in the pom that shouldn't be there? I don't think
there's anything too crazy in the pom that should cause it to be
generating weird artifacts. Is it something in the parent pom?
>
> Niall
>
> On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> > All,
> >
> > I have prepared a commons-proxy-1.0-rc2 release candidate. The
> > distribution files can be found at:
> >
> > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
> >
> > and the site can be found at:
> >
> > http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
> >
> > The SVN tag used to create the release can be found at:
> >
> > http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
> >
> > All issues brought up thus far with the first release candidate have
> > been addressed. Again, this is my first release (including signing),
> > so please review thoroughly (not that you normally don't).
> >
> > Thank you,
> >
> > James Carman
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Proxy 1.0 (from rc2)
Posted by Niall Pemberton <ni...@gmail.com>.
I'm +0 on this release because I like to review the actual artifacts
that are going to be distributed. The distros IMO meet ASF release
requirements but if I run command "mvn -Prc site assembly:assembly"
then the binary distro created also includes the javadocs and also
-sources.jar and -javadoc.jar. Which kind of makes the argument for
reviewing actual artifacts.
Niall
On Feb 19, 2008 11:31 PM, James Carman <ja...@carmanconsulting.com> wrote:
> All,
>
> I have prepared a commons-proxy-1.0-rc2 release candidate. The
> distribution files can be found at:
>
> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/
>
> and the site can be found at:
>
> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site
>
> The SVN tag used to create the release can be found at:
>
> http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2
>
> All issues brought up thus far with the first release candidate have
> been addressed. Again, this is my first release (including signing),
> so please review thoroughly (not that you normally don't).
>
> Thank you,
>
> James Carman
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org