Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
+1 ...ant On Fri, Jan 14, 2011 at 1:41 PM, Oleg Kalnichevski wrote: > Please vote on releasing these packages as HttpComponents AsyncClient > 4.0-alpha1.The vote is open for the at least 72 hours, and only votes > from HttpComponents PMC members are binding. The vote passes if at least > three binding +1 votes are cast and there are more +1 than -1 votes. > > Packages: > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/ > > Release notes: > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/RELEASE_NOTES.txt > > Maven artefacts: > https://repository.apache.org/content/repositories/orgapachehttpcomponents-028/org/apache/httpcomponents/ > > SVN tag: > http://svn.apache.org/repos/asf/httpcomponents/httpasyncclient/tags/4.0-alpha1-RC1/ > > -- > Vote: HttpComponents AsyncClient 4.0-alpha1 release > [ ] +1 Release the packages as HttpComponents AsyncClient 4.0-alpha1. > [ ] -1 I am against releasing the packages (must include a reason). > > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
I support releasing these as alpha1. Paul On Fri, Jan 14, 2011 at 6:12 PM, Oleg Kalnichevski wrote: > On Fri, 2011-01-14 at 18:05 +, sebb wrote: >> On 14 January 2011 13:41, Oleg Kalnichevski wrote: >> > Please vote on releasing these packages as HttpComponents AsyncClient >> > 4.0-alpha1.The vote is open for the at least 72 hours, and only votes >> > from HttpComponents PMC members are binding. The vote passes if at least >> > three binding +1 votes are cast and there are more +1 than -1 votes. >> > >> > Packages: >> > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/ >> >> The source jar manifest does not have all the usual headers. Not a >> blocker, but should be fixed for next release (or if this RC fails). >> >> The README file does not say what the HttpAsynchClient actually is - >> one can hazard a guess from the name, but it would be better if there >> was a short description. Again, not a blocker. >> >> The binary release includes httpclient-4.1-beta1.jar. Given that there >> is currently a vote to release httpclient 4.1GA, it might be better to >> wait until that is available, and then vote on releasing with the new >> jar. >> >> For that reason, I vote -0. >> >> Release otherwise seems OK - builds and tests OK for me. >> > > HAC is still in an early alpha phase of development. I think it is more > important to release it early and get feedback on the API than to pick > up the latest code from HC, which is the reason why I thought it would > make sense to release both components at the same time. > > I can fix the two non-blockers if that makes you reconsider. > > Oleg > > > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [email protected] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
Vote: HttpComponents AsyncClient 4.0-alpha1 release [X] +1 Release the packages as HttpComponents AsyncClient 4.0-alpha1. [ ] -1 I am against releasing the packages (must include a reason). I agree that early feedback would be what's more beneficial for the AsyncClient at this time.. Hence the release in alpha state is something good. I personally have been wanting to try it out for sometime, but unfortunately not been lucky with time - but the release may be able to pull in new users asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
On Fri, 2011-01-14 at 18:05 +, sebb wrote: > On 14 January 2011 13:41, Oleg Kalnichevski wrote: > > Please vote on releasing these packages as HttpComponents AsyncClient > > 4.0-alpha1.The vote is open for the at least 72 hours, and only votes > > from HttpComponents PMC members are binding. The vote passes if at least > > three binding +1 votes are cast and there are more +1 than -1 votes. > > > > Packages: > > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/ > > The source jar manifest does not have all the usual headers. Not a > blocker, but should be fixed for next release (or if this RC fails). > > The README file does not say what the HttpAsynchClient actually is - > one can hazard a guess from the name, but it would be better if there > was a short description. Again, not a blocker. > > The binary release includes httpclient-4.1-beta1.jar. Given that there > is currently a vote to release httpclient 4.1GA, it might be better to > wait until that is available, and then vote on releasing with the new > jar. > > For that reason, I vote -0. > > Release otherwise seems OK - builds and tests OK for me. > HAC is still in an early alpha phase of development. I think it is more important to release it early and get feedback on the API than to pick up the latest code from HC, which is the reason why I thought it would make sense to release both components at the same time. I can fix the two non-blockers if that makes you reconsider. Oleg - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
On 14 January 2011 13:41, Oleg Kalnichevski wrote: > Please vote on releasing these packages as HttpComponents AsyncClient > 4.0-alpha1.The vote is open for the at least 72 hours, and only votes > from HttpComponents PMC members are binding. The vote passes if at least > three binding +1 votes are cast and there are more +1 than -1 votes. > > Packages: > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/ The source jar manifest does not have all the usual headers. Not a blocker, but should be fixed for next release (or if this RC fails). The README file does not say what the HttpAsynchClient actually is - one can hazard a guess from the name, but it would be better if there was a short description. Again, not a blocker. The binary release includes httpclient-4.1-beta1.jar. Given that there is currently a vote to release httpclient 4.1GA, it might be better to wait until that is available, and then vote on releasing with the new jar. For that reason, I vote -0. Release otherwise seems OK - builds and tests OK for me. > Release notes: > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/RELEASE_NOTES.txt > > Maven artefacts: > https://repository.apache.org/content/repositories/orgapachehttpcomponents-028/org/apache/httpcomponents/ > > SVN tag: > http://svn.apache.org/repos/asf/httpcomponents/httpasyncclient/tags/4.0-alpha1-RC1/ > > -- > Vote: HttpComponents AsyncClient 4.0-alpha1 release > [ ] +1 Release the packages as HttpComponents AsyncClient 4.0-alpha1. > [ ] -1 I am against releasing the packages (must include a reason). > > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: Voting on releases; Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
On 14 January 2011 15:40, Oleg Kalnichevski wrote: > On Fri, 2011-01-14 at 15:13 +, Moore, Jonathan wrote: >> As a general rule, what should I be looking at as an "informed voter"? I'm >> pretty familiar with the contents of the caching module, and think the >> content there is ready for release...is that enough for the vote, or do we >> also double-check the artifacts (I.e. Do we verify maven did its job >> right, etc.)? What else do people look at? >> > > There are no specific guidelines I know of. Various people look at > various things prior to casting a vote. I personally mostly rely on my > gut feel. If I have been following a project on a regular basis and am > convinced its design / architecture / QA process are adequate and > believe that the particular piece of code being released is in a good > shape I usually check only a few things, such as whether or not the > release artifacts can be built from source distribution and the > resultant artifacts meet ASL legal requirements (NOTICE and LICENSE bits > are present, etc). Given those criteria I feel comfortable casting a > vote. Also, the source archives should not contain anything that is not in the SVN tag (or is at least derivable from the tag). Ideally try building and testing on a variety of different platforms and JVMs - in particular the target JVM! I also check the hashes and signatures, and that the zip / tar.gz archives agree with each other. [Automatic hash generation was broken in one Maven version - since fixed] Sigs must use a key that is in KEYS and available from key servers. > By the way: we DO encourage all members of the community to cast a vote > on releases even if their votes are non binding. Often a PMC member with > a binding vote may decide to vote differently based on feedback given by > other people. +1 It's always useful to know if others can successfully build and test the code - or not, as sometimes happens! > Cheers > > Oleg > > > > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Voting on releases; Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
On Fri, 2011-01-14 at 15:13 +, Moore, Jonathan wrote: > As a general rule, what should I be looking at as an "informed voter"? I'm > pretty familiar with the contents of the caching module, and think the > content there is ready for release...is that enough for the vote, or do we > also double-check the artifacts (I.e. Do we verify maven did its job > right, etc.)? What else do people look at? > There are no specific guidelines I know of. Various people look at various things prior to casting a vote. I personally mostly rely on my gut feel. If I have been following a project on a regular basis and am convinced its design / architecture / QA process are adequate and believe that the particular piece of code being released is in a good shape I usually check only a few things, such as whether or not the release artifacts can be built from source distribution and the resultant artifacts meet ASL legal requirements (NOTICE and LICENSE bits are present, etc). Given those criteria I feel comfortable casting a vote. By the way: we DO encourage all members of the community to cast a vote on releases even if their votes are non binding. Often a PMC member with a binding vote may decide to vote differently based on feedback given by other people. Cheers Oleg - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
As a general rule, what should I be looking at as an "informed voter"? I'm pretty familiar with the contents of the caching module, and think the content there is ready for release...is that enough for the vote, or do we also double-check the artifacts (I.e. Do we verify maven did its job right, etc.)? What else do people look at? Jon Jon Moore Comcast Interactive Media On 1/14/11 8:41 AM, "Oleg Kalnichevski" wrote: >Please vote on releasing these packages as HttpComponents AsyncClient >4.0-alpha1.The vote is open for the at least 72 hours, and only votes >from HttpComponents PMC members are binding. The vote passes if at least >three binding +1 votes are cast and there are more +1 than -1 votes. > >Packages: >http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/ > >Release notes: >http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/RELEASE_NOTES.t >xt > >Maven artefacts: >https://repository.apache.org/content/repositories/orgapachehttpcomponents >-028/org/apache/httpcomponents/ > >SVN tag: >http://svn.apache.org/repos/asf/httpcomponents/httpasyncclient/tags/4.0-al >pha1-RC1/ > >-- > Vote: HttpComponents AsyncClient 4.0-alpha1 release > [ ] +1 Release the packages as HttpComponents AsyncClient 4.0-alpha1. > [ ] -1 I am against releasing the packages (must include a reason). > > >- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
Re: [VOTE] HttpComponents AsyncClient 4.0-alpha1 release based on RC1
[x] +1 Release the packages as HttpComponents AsyncClient 4.0-alpha1 On Fri, 2011-01-14 at 14:41 +0100, Oleg Kalnichevski wrote: > Please vote on releasing these packages as HttpComponents AsyncClient > 4.0-alpha1.The vote is open for the at least 72 hours, and only votes > from HttpComponents PMC members are binding. The vote passes if at least > three binding +1 votes are cast and there are more +1 than -1 votes. > > Packages: > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/ > > Release notes: > http://people.apache.org/~olegk/httpasyncclient-4.0-alpha1/RELEASE_NOTES.txt > > Maven artefacts: > https://repository.apache.org/content/repositories/orgapachehttpcomponents-028/org/apache/httpcomponents/ > > SVN tag: > http://svn.apache.org/repos/asf/httpcomponents/httpasyncclient/tags/4.0-alpha1-RC1/ > > -- > Vote: HttpComponents AsyncClient 4.0-alpha1 release > [ ] +1 Release the packages as HttpComponents AsyncClient 4.0-alpha1. > [ ] -1 I am against releasing the packages (must include a reason). > > > - > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
