You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2010/05/12 23:53:00 UTC
[VOTE] HttpComponents Client 4.1-alpha2 release
Please vote on releasing these packages as HttpComponents Client
4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
Release notes:
http://people.apache.org/~olegk/httpclient-4.1-alpha2/RELEASE_NOTES.txt
Release tag:
http://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.1-alpha2/
--------------------------------------------------------------------------
Vote: HttpComponents Client 4.1-alpha2 release
[ ] +1 Release the packages as HttpComponents Client 4.1-alpha2.
[ ] -1 I am against releasing the packages (must include a reason).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by ant elder <an...@gmail.com>.
On Thu, May 13, 2010 at 5:34 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 17:29 +0100, sebb wrote:
>> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> > On Thu, 2010-05-13 at 16:49 +0100, sebb wrote:
>> > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> > > > On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
>> > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> > > > > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
>> > > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> > > > > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
>> > > > > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> > > > > > > > > > Please vote on releasing these packages as HttpComponents Client
>> > > > > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
>> > > > > > > > >
>> > > > > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
>> > > > > > > > >
>> > > > > > > > > Should be largely a formality if the main packages are OK, but they do
>> > > > > > > > > need to be voted on.
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > Sebastian, we have been through that, haven't we? Only source package
>> > > > > > > > represents an official release artifact that needs to be voted on.
>> > > > > > >
>> > > > > > > The Maven artifacts always include source files, either as source jars
>> > > > > > > (which should be provided), if not then at least pom.xml will be
>> > > > > > > included.
>> > > > > > >
>> > > > > > > > Binary artifacts are merely byproducts. If you want to verify they are
>> > > > > > > > ok, you should build them from source.
>> > > > > > >
>> > > > > > > That's not strictly true either - binary artifacts need to be
>> > > > > > > inspected to ensure that the appropriate N&L files are present.
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Please see
>> > > > > > https://issues.apache.org/jira/browse/LEGAL-34
>> > > > > >
>> > > > >
>> > > > > Which was never really resolved and anyway does not cover the point
>> > > > > about N&L at all.
>> > > > >
>> > > >
>> > > >
>> > > > Precisely. Hen's statement boils down to a simple fact that there is no
>> > > > ASF wide policy on the matter and it is up to individual projects unless
>> > > > the Board rules otherwise.
>> > > >
>> > > >
>> > > > > >
>> > > > > > > > My main problem is not with uploading a bunch of files, but the fact you
>> > > > > > > > are changing an established release process in the middle of a release
>> > > > > > > > without prior discussion and a consent from other committers.
>> > > > > > >
>> > > > > > > My point is that the process is IMO not following the ASF standard,
>> > > > > > > and therefore needs to be fixed.
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > There is no ASF standard. It is up to individual projects. Please see
>> > > > > > https://issues.apache.org/jira/browse/LEGAL-34
>> > > > >
>> > > > > Not really relevant as source releases must be approved by the PMC.
>> > > > > The Maven artefacts include source, and therefore must be voted on.
>> > > > >
>> > > >
>> > > >
>> > > > Is there an official statement to that effect by the Board I could have
>> > > > a look at?
>> > > >
>> > >
>> > > No idea.
>> > >
>> > > But I hope it's agreed that source releases must be voted on by the PMC.
>> > > Maven includes source, and is a release.
>> > >
>> > > >
>> > > > > Regardless of the JIRA issue, I think the consumers of ASF releases
>> > > > > have a right to expect that the archives etc have been formally
>> > > > > approved as part of the "quality control" applied by the ASF
>> > > > > organisation.
>> > > > >
>> > > > > Why not just publish the Maven artefacts so we can include them in the vote?
>> > > > >
>> > > >
>> > > >
>> > > > How exactly do you suggest that I do that, as the artifacts are
>> > > > generated by Maven from source at deployment time?
>> > >
>> > > This is actually quite easy, see
>> > > https://issues.apache.org/jira/browse/COMMONSSITE-55
>> > >
>> > > > Besides, the release process is already is painful enough. I see no good
>> > > > reason for making it even more painful due to some completely arbitrary
>> > > > requirement.
>> > >
>> > > It's not arbitrary.
>> > >
>> >
>> >
>> > I am sorry, Sebastian, but per comment from legal unless the Board makes
>> > a clear statement, it is just arbitrary
>>
>> Source releases still require PMC votes.
>>
>
> Sure, that is why there are source packages (zip and tarball).
>
Yes and i think thats the difference between this type of release and
things like the maven plugin releases which are just published as jars
in the maven repository and nothing else so there is no easy way to
recreate the jar. With this type of release there is a source
distribution published and you can use that to recreate all the binary
artifacts.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 17:50 +0100, sebb wrote:
> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > On Thu, 2010-05-13 at 17:29 +0100, sebb wrote:
> > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > On Thu, 2010-05-13 at 16:49 +0100, sebb wrote:
> > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> > > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > > > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > > > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > > > > > > > >
> > > > > > > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > > > > > > > >
> > > > > > > > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > > > > > > > need to be voted on.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Sebastian, we have been through that, haven't we? Only source package
> > > > > > > > > > represents an official release artifact that needs to be voted on.
> > > > > > > > >
> > > > > > > > > The Maven artifacts always include source files, either as source jars
> > > > > > > > > (which should be provided), if not then at least pom.xml will be
> > > > > > > > > included.
> > > > > > > > >
> > > > > > > > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > > > > > > > ok, you should build them from source.
> > > > > > > > >
> > > > > > > > > That's not strictly true either - binary artifacts need to be
> > > > > > > > > inspected to ensure that the appropriate N&L files are present.
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Please see
> > > > > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > > > > >
> > > > > > >
> > > > > > > Which was never really resolved and anyway does not cover the point
> > > > > > > about N&L at all.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Precisely. Hen's statement boils down to a simple fact that there is no
> > > > > > ASF wide policy on the matter and it is up to individual projects unless
> > > > > > the Board rules otherwise.
> > > > > >
> > > > > >
> > > > > > > >
> > > > > > > > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > > > > > > > are changing an established release process in the middle of a release
> > > > > > > > > > without prior discussion and a consent from other committers.
> > > > > > > > >
> > > > > > > > > My point is that the process is IMO not following the ASF standard,
> > > > > > > > > and therefore needs to be fixed.
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > There is no ASF standard. It is up to individual projects. Please see
> > > > > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > > > >
> > > > > > > Not really relevant as source releases must be approved by the PMC.
> > > > > > > The Maven artefacts include source, and therefore must be voted on.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Is there an official statement to that effect by the Board I could have
> > > > > > a look at?
> > > > > >
> > > > >
> > > > > No idea.
> > > > >
> > > > > But I hope it's agreed that source releases must be voted on by the PMC.
> > > > > Maven includes source, and is a release.
> > > > >
> > > > > >
> > > > > > > Regardless of the JIRA issue, I think the consumers of ASF releases
> > > > > > > have a right to expect that the archives etc have been formally
> > > > > > > approved as part of the "quality control" applied by the ASF
> > > > > > > organisation.
> > > > > > >
> > > > > > > Why not just publish the Maven artefacts so we can include them in the vote?
> > > > > > >
> > > > > >
> > > > > >
> > > > > > How exactly do you suggest that I do that, as the artifacts are
> > > > > > generated by Maven from source at deployment time?
> > > > >
> > > > > This is actually quite easy, see
> > > > > https://issues.apache.org/jira/browse/COMMONSSITE-55
> > > > >
> > > > > > Besides, the release process is already is painful enough. I see no good
> > > > > > reason for making it even more painful due to some completely arbitrary
> > > > > > requirement.
> > > > >
> > > > > It's not arbitrary.
> > > > >
> > > >
> > > >
> > > > I am sorry, Sebastian, but per comment from legal unless the Board makes
> > > > a clear statement, it is just arbitrary
> > >
> > > Source releases still require PMC votes.
> > >
> >
> >
> > Sure, that is why there are source packages (zip and tarball).
>
> The Maven release includes source, but is not identical to the above,
> so we need to vote on that as well.
>
Not unless the Board or PMC decide so.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 17:29 +0100, sebb wrote:
> > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > On Thu, 2010-05-13 at 16:49 +0100, sebb wrote:
> > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > > > > > > >
> > > > > > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > > > > > > >
> > > > > > > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > > > > > > need to be voted on.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Sebastian, we have been through that, haven't we? Only source package
> > > > > > > > > represents an official release artifact that needs to be voted on.
> > > > > > > >
> > > > > > > > The Maven artifacts always include source files, either as source jars
> > > > > > > > (which should be provided), if not then at least pom.xml will be
> > > > > > > > included.
> > > > > > > >
> > > > > > > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > > > > > > ok, you should build them from source.
> > > > > > > >
> > > > > > > > That's not strictly true either - binary artifacts need to be
> > > > > > > > inspected to ensure that the appropriate N&L files are present.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Please see
> > > > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > > > >
> > > > > >
> > > > > > Which was never really resolved and anyway does not cover the point
> > > > > > about N&L at all.
> > > > > >
> > > > >
> > > > >
> > > > > Precisely. Hen's statement boils down to a simple fact that there is no
> > > > > ASF wide policy on the matter and it is up to individual projects unless
> > > > > the Board rules otherwise.
> > > > >
> > > > >
> > > > > > >
> > > > > > > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > > > > > > are changing an established release process in the middle of a release
> > > > > > > > > without prior discussion and a consent from other committers.
> > > > > > > >
> > > > > > > > My point is that the process is IMO not following the ASF standard,
> > > > > > > > and therefore needs to be fixed.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > There is no ASF standard. It is up to individual projects. Please see
> > > > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > > >
> > > > > > Not really relevant as source releases must be approved by the PMC.
> > > > > > The Maven artefacts include source, and therefore must be voted on.
> > > > > >
> > > > >
> > > > >
> > > > > Is there an official statement to that effect by the Board I could have
> > > > > a look at?
> > > > >
> > > >
> > > > No idea.
> > > >
> > > > But I hope it's agreed that source releases must be voted on by the PMC.
> > > > Maven includes source, and is a release.
> > > >
> > > > >
> > > > > > Regardless of the JIRA issue, I think the consumers of ASF releases
> > > > > > have a right to expect that the archives etc have been formally
> > > > > > approved as part of the "quality control" applied by the ASF
> > > > > > organisation.
> > > > > >
> > > > > > Why not just publish the Maven artefacts so we can include them in the vote?
> > > > > >
> > > > >
> > > > >
> > > > > How exactly do you suggest that I do that, as the artifacts are
> > > > > generated by Maven from source at deployment time?
> > > >
> > > > This is actually quite easy, see
> > > > https://issues.apache.org/jira/browse/COMMONSSITE-55
> > > >
> > > > > Besides, the release process is already is painful enough. I see no good
> > > > > reason for making it even more painful due to some completely arbitrary
> > > > > requirement.
> > > >
> > > > It's not arbitrary.
> > > >
> > >
> > >
> > > I am sorry, Sebastian, but per comment from legal unless the Board makes
> > > a clear statement, it is just arbitrary
> >
> > Source releases still require PMC votes.
> >
>
>
> Sure, that is why there are source packages (zip and tarball).
The Maven release includes source, but is not identical to the above,
so we need to vote on that as well.
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 17:29 +0100, sebb wrote:
> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > On Thu, 2010-05-13 at 16:49 +0100, sebb wrote:
> > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > > > > > >
> > > > > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > > > > > >
> > > > > > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > > > > > need to be voted on.
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Sebastian, we have been through that, haven't we? Only source package
> > > > > > > > represents an official release artifact that needs to be voted on.
> > > > > > >
> > > > > > > The Maven artifacts always include source files, either as source jars
> > > > > > > (which should be provided), if not then at least pom.xml will be
> > > > > > > included.
> > > > > > >
> > > > > > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > > > > > ok, you should build them from source.
> > > > > > >
> > > > > > > That's not strictly true either - binary artifacts need to be
> > > > > > > inspected to ensure that the appropriate N&L files are present.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Please see
> > > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > > >
> > > > >
> > > > > Which was never really resolved and anyway does not cover the point
> > > > > about N&L at all.
> > > > >
> > > >
> > > >
> > > > Precisely. Hen's statement boils down to a simple fact that there is no
> > > > ASF wide policy on the matter and it is up to individual projects unless
> > > > the Board rules otherwise.
> > > >
> > > >
> > > > > >
> > > > > > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > > > > > are changing an established release process in the middle of a release
> > > > > > > > without prior discussion and a consent from other committers.
> > > > > > >
> > > > > > > My point is that the process is IMO not following the ASF standard,
> > > > > > > and therefore needs to be fixed.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > There is no ASF standard. It is up to individual projects. Please see
> > > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > >
> > > > > Not really relevant as source releases must be approved by the PMC.
> > > > > The Maven artefacts include source, and therefore must be voted on.
> > > > >
> > > >
> > > >
> > > > Is there an official statement to that effect by the Board I could have
> > > > a look at?
> > > >
> > >
> > > No idea.
> > >
> > > But I hope it's agreed that source releases must be voted on by the PMC.
> > > Maven includes source, and is a release.
> > >
> > > >
> > > > > Regardless of the JIRA issue, I think the consumers of ASF releases
> > > > > have a right to expect that the archives etc have been formally
> > > > > approved as part of the "quality control" applied by the ASF
> > > > > organisation.
> > > > >
> > > > > Why not just publish the Maven artefacts so we can include them in the vote?
> > > > >
> > > >
> > > >
> > > > How exactly do you suggest that I do that, as the artifacts are
> > > > generated by Maven from source at deployment time?
> > >
> > > This is actually quite easy, see
> > > https://issues.apache.org/jira/browse/COMMONSSITE-55
> > >
> > > > Besides, the release process is already is painful enough. I see no good
> > > > reason for making it even more painful due to some completely arbitrary
> > > > requirement.
> > >
> > > It's not arbitrary.
> > >
> >
> >
> > I am sorry, Sebastian, but per comment from legal unless the Board makes
> > a clear statement, it is just arbitrary
>
> Source releases still require PMC votes.
>
Sure, that is why there are source packages (zip and tarball).
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 16:49 +0100, sebb wrote:
> > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > > > > >
> > > > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > > > > >
> > > > > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > > > > need to be voted on.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Sebastian, we have been through that, haven't we? Only source package
> > > > > > > represents an official release artifact that needs to be voted on.
> > > > > >
> > > > > > The Maven artifacts always include source files, either as source jars
> > > > > > (which should be provided), if not then at least pom.xml will be
> > > > > > included.
> > > > > >
> > > > > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > > > > ok, you should build them from source.
> > > > > >
> > > > > > That's not strictly true either - binary artifacts need to be
> > > > > > inspected to ensure that the appropriate N&L files are present.
> > > > > >
> > > > >
> > > > >
> > > > > Please see
> > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > > >
> > > >
> > > > Which was never really resolved and anyway does not cover the point
> > > > about N&L at all.
> > > >
> > >
> > >
> > > Precisely. Hen's statement boils down to a simple fact that there is no
> > > ASF wide policy on the matter and it is up to individual projects unless
> > > the Board rules otherwise.
> > >
> > >
> > > > >
> > > > > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > > > > are changing an established release process in the middle of a release
> > > > > > > without prior discussion and a consent from other committers.
> > > > > >
> > > > > > My point is that the process is IMO not following the ASF standard,
> > > > > > and therefore needs to be fixed.
> > > > > >
> > > > >
> > > > >
> > > > > There is no ASF standard. It is up to individual projects. Please see
> > > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > >
> > > > Not really relevant as source releases must be approved by the PMC.
> > > > The Maven artefacts include source, and therefore must be voted on.
> > > >
> > >
> > >
> > > Is there an official statement to that effect by the Board I could have
> > > a look at?
> > >
> >
> > No idea.
> >
> > But I hope it's agreed that source releases must be voted on by the PMC.
> > Maven includes source, and is a release.
> >
> > >
> > > > Regardless of the JIRA issue, I think the consumers of ASF releases
> > > > have a right to expect that the archives etc have been formally
> > > > approved as part of the "quality control" applied by the ASF
> > > > organisation.
> > > >
> > > > Why not just publish the Maven artefacts so we can include them in the vote?
> > > >
> > >
> > >
> > > How exactly do you suggest that I do that, as the artifacts are
> > > generated by Maven from source at deployment time?
> >
> > This is actually quite easy, see
> > https://issues.apache.org/jira/browse/COMMONSSITE-55
> >
> > > Besides, the release process is already is painful enough. I see no good
> > > reason for making it even more painful due to some completely arbitrary
> > > requirement.
> >
> > It's not arbitrary.
> >
>
>
> I am sorry, Sebastian, but per comment from legal unless the Board makes
> a clear statement, it is just arbitrary
Source releases still require PMC votes.
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 16:49 +0100, sebb wrote:
> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > > > >
> > > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > > > >
> > > > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > > > need to be voted on.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Sebastian, we have been through that, haven't we? Only source package
> > > > > > represents an official release artifact that needs to be voted on.
> > > > >
> > > > > The Maven artifacts always include source files, either as source jars
> > > > > (which should be provided), if not then at least pom.xml will be
> > > > > included.
> > > > >
> > > > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > > > ok, you should build them from source.
> > > > >
> > > > > That's not strictly true either - binary artifacts need to be
> > > > > inspected to ensure that the appropriate N&L files are present.
> > > > >
> > > >
> > > >
> > > > Please see
> > > > https://issues.apache.org/jira/browse/LEGAL-34
> > > >
> > >
> > > Which was never really resolved and anyway does not cover the point
> > > about N&L at all.
> > >
> >
> >
> > Precisely. Hen's statement boils down to a simple fact that there is no
> > ASF wide policy on the matter and it is up to individual projects unless
> > the Board rules otherwise.
> >
> >
> > > >
> > > > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > > > are changing an established release process in the middle of a release
> > > > > > without prior discussion and a consent from other committers.
> > > > >
> > > > > My point is that the process is IMO not following the ASF standard,
> > > > > and therefore needs to be fixed.
> > > > >
> > > >
> > > >
> > > > There is no ASF standard. It is up to individual projects. Please see
> > > > https://issues.apache.org/jira/browse/LEGAL-34
> > >
> > > Not really relevant as source releases must be approved by the PMC.
> > > The Maven artefacts include source, and therefore must be voted on.
> > >
> >
> >
> > Is there an official statement to that effect by the Board I could have
> > a look at?
> >
>
> No idea.
>
> But I hope it's agreed that source releases must be voted on by the PMC.
> Maven includes source, and is a release.
>
> >
> > > Regardless of the JIRA issue, I think the consumers of ASF releases
> > > have a right to expect that the archives etc have been formally
> > > approved as part of the "quality control" applied by the ASF
> > > organisation.
> > >
> > > Why not just publish the Maven artefacts so we can include them in the vote?
> > >
> >
> >
> > How exactly do you suggest that I do that, as the artifacts are
> > generated by Maven from source at deployment time?
>
> This is actually quite easy, see
> https://issues.apache.org/jira/browse/COMMONSSITE-55
>
> > Besides, the release process is already is painful enough. I see no good
> > reason for making it even more painful due to some completely arbitrary
> > requirement.
>
> It's not arbitrary.
>
I am sorry, Sebastian, but per comment from legal unless the Board makes
a clear statement, it is just arbitrary
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by ant elder <an...@apache.org>.
On Fri, May 14, 2010 at 4:22 PM, sebb <se...@gmail.com> wrote:
> On 14/05/2010, ant elder <an...@gmail.com> wrote:
>> On Fri, May 14, 2010 at 11:19 AM, sebb <se...@gmail.com> wrote:
>> > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> >> On Thu, 2010-05-13 at 17:55 +0100, sebb wrote:
>> >> > On 13/05/2010, ant elder <an...@gmail.com> wrote:
>> >> > > On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
>> >> > >
>> >> > >
>> >> > > >
>> >> > > > This is actually quite easy, see
>> >> > > > https://issues.apache.org/jira/browse/COMMONSSITE-55
>> >> > > >
>> >> > >
>> >> > >
>> >> > > Thanks for the pointer, i didn't know you could do use a file url in
>> >> > > altDeploymentRepository.
>> >> > >
>> >> >
>> >> > BTW, you can also add the profile to your local settings.xml.
>> >> >
>> >> > Though if many people may want to use the same method, it is more
>> >> > efficient to add it to a shared resource such a a parent pom.
>> >> >
>> >>
>> >>
>> >> This approach results in corrupt / inconsistent maven metadata
>> >> (maven-metadata.xml) unless the metadata is manually copied over.
>> >>
>> >
>> > This is what the Apache Nexus repo is for, see:
>> >
>> > http://maven.apache.org/developers/release/apache-release.html
>> >
>> > [As far as I can tell, one can use deploy to upload to the repo if one
>> > does not use the release plugin.]
>> >
>> > PMC then votes on the repo contents, which are then either promoted or dropped.
>> >
>> > ==
>> >
>> > Note that I raised the issue of whether Maven sources need to be voted
>> > on with the board/infrastructure.
>> >
>> > All the responses say that Maven source packages need to be voted on
>> > by the PMC, and this is supported by the updated releases FAQ at:
>> >
>> > http://www.apache.org/dev/release.html
>> >
>> > This also requires jars etc. to have N&L files, which implies that the
>> > Maven artifacts also need to be reviewed.
>> >
>> > Voting on source releases is not an issue that is decided by PMCs; it
>> > is mandated by the ASF.
>> >
>> >> Oleg
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> >> For additional commands, e-mail: dev-help@hc.apache.org
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> > For additional commands, e-mail: dev-help@hc.apache.org
>> >
>> >
>>
>>
>> Sebb, there is a source release that we're voting on, so,
>> respectfully, i don't think this is an issue. I'm on the board and
>> infrastructure lists so have seen the discussion you mention. The key
>> point is that all ASF releases must include a source release and any
>> other binary artifacts are an optional convenience.
>
> Here, I entirely agree - I have no problem with the source and binary
> archives being released to the ASF Mirror system once the PMC has
> approved it.
>
>> The issue with the Maven artifacts requiring source artifacts came
>> from projects that were doing pure Maven artifact only releases where
>> the jars in the Maven repository did not have an associated source
>> release so there was no way to recreate the Maven artifact jars from
>> the release. Thats not the case here as there is a source release and
>> building that creates all the Maven artifacts, so it does not matter
>> whether or not those individual Maven artifact jars themselves have
>> associated source artifacts.
>
> However, I do have a problem with not submitting the Maven artifacts for a vote.
>
> The artifacts are a formal release, and therefore must be approved by the PMC.
>
> They contain source files, and my reading of the FAQ says that source
> releases must be voted on.
>
Well, i think that can depend on how you look at them - just because
they contain source does not make them a or the source release. The
canonical source release is the
httpcomponents-client-4.1-alpha2-src.zip/tar.gz, all the binary
artifacts are generated from that and things like
httpclient-4.1-alpha2-sources.jar are just one of the optional
generated artifacts.
> Also, the Release FAQ makes demands on the contents of all releases.
> Regardless of the requirement to vote on the sources, it seems to me
> that the best way to check that these requirements are met is to put
> the artifacts up for inspection by the PMC.
>
Sure i don't actually disagree but i don't think getting that to
happen needs to delay or block release votes until its done, someone
needs to go work it all out and set it up and document the new release
process which works with out complexity, and if if that happens I
expect people would use it.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 14/05/2010, ant elder <an...@gmail.com> wrote:
> On Fri, May 14, 2010 at 11:19 AM, sebb <se...@gmail.com> wrote:
> > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> >> On Thu, 2010-05-13 at 17:55 +0100, sebb wrote:
> >> > On 13/05/2010, ant elder <an...@gmail.com> wrote:
> >> > > On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
> >> > >
> >> > >
> >> > > >
> >> > > > This is actually quite easy, see
> >> > > > https://issues.apache.org/jira/browse/COMMONSSITE-55
> >> > > >
> >> > >
> >> > >
> >> > > Thanks for the pointer, i didn't know you could do use a file url in
> >> > > altDeploymentRepository.
> >> > >
> >> >
> >> > BTW, you can also add the profile to your local settings.xml.
> >> >
> >> > Though if many people may want to use the same method, it is more
> >> > efficient to add it to a shared resource such a a parent pom.
> >> >
> >>
> >>
> >> This approach results in corrupt / inconsistent maven metadata
> >> (maven-metadata.xml) unless the metadata is manually copied over.
> >>
> >
> > This is what the Apache Nexus repo is for, see:
> >
> > http://maven.apache.org/developers/release/apache-release.html
> >
> > [As far as I can tell, one can use deploy to upload to the repo if one
> > does not use the release plugin.]
> >
> > PMC then votes on the repo contents, which are then either promoted or dropped.
> >
> > ==
> >
> > Note that I raised the issue of whether Maven sources need to be voted
> > on with the board/infrastructure.
> >
> > All the responses say that Maven source packages need to be voted on
> > by the PMC, and this is supported by the updated releases FAQ at:
> >
> > http://www.apache.org/dev/release.html
> >
> > This also requires jars etc. to have N&L files, which implies that the
> > Maven artifacts also need to be reviewed.
> >
> > Voting on source releases is not an issue that is decided by PMCs; it
> > is mandated by the ASF.
> >
> >> Oleg
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> >> For additional commands, e-mail: dev-help@hc.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> > For additional commands, e-mail: dev-help@hc.apache.org
> >
> >
>
>
> Sebb, there is a source release that we're voting on, so,
> respectfully, i don't think this is an issue. I'm on the board and
> infrastructure lists so have seen the discussion you mention. The key
> point is that all ASF releases must include a source release and any
> other binary artifacts are an optional convenience.
Here, I entirely agree - I have no problem with the source and binary
archives being released to the ASF Mirror system once the PMC has
approved it.
> The issue with the Maven artifacts requiring source artifacts came
> from projects that were doing pure Maven artifact only releases where
> the jars in the Maven repository did not have an associated source
> release so there was no way to recreate the Maven artifact jars from
> the release. Thats not the case here as there is a source release and
> building that creates all the Maven artifacts, so it does not matter
> whether or not those individual Maven artifact jars themselves have
> associated source artifacts.
However, I do have a problem with not submitting the Maven artifacts for a vote.
The artifacts are a formal release, and therefore must be approved by the PMC.
They contain source files, and my reading of the FAQ says that source
releases must be voted on.
Also, the Release FAQ makes demands on the contents of all releases.
Regardless of the requirement to vote on the sources, it seems to me
that the best way to check that these requirements are met is to put
the artifacts up for inspection by the PMC.
> I'm still +1 on this release.
>
>
> ...ant
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by ant elder <an...@gmail.com>.
On Fri, May 14, 2010 at 11:19 AM, sebb <se...@gmail.com> wrote:
> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
>> On Thu, 2010-05-13 at 17:55 +0100, sebb wrote:
>> > On 13/05/2010, ant elder <an...@gmail.com> wrote:
>> > > On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
>> > >
>> > >
>> > > >
>> > > > This is actually quite easy, see
>> > > > https://issues.apache.org/jira/browse/COMMONSSITE-55
>> > > >
>> > >
>> > >
>> > > Thanks for the pointer, i didn't know you could do use a file url in
>> > > altDeploymentRepository.
>> > >
>> >
>> > BTW, you can also add the profile to your local settings.xml.
>> >
>> > Though if many people may want to use the same method, it is more
>> > efficient to add it to a shared resource such a a parent pom.
>> >
>>
>>
>> This approach results in corrupt / inconsistent maven metadata
>> (maven-metadata.xml) unless the metadata is manually copied over.
>>
>
> This is what the Apache Nexus repo is for, see:
>
> http://maven.apache.org/developers/release/apache-release.html
>
> [As far as I can tell, one can use deploy to upload to the repo if one
> does not use the release plugin.]
>
> PMC then votes on the repo contents, which are then either promoted or dropped.
>
> ==
>
> Note that I raised the issue of whether Maven sources need to be voted
> on with the board/infrastructure.
>
> All the responses say that Maven source packages need to be voted on
> by the PMC, and this is supported by the updated releases FAQ at:
>
> http://www.apache.org/dev/release.html
>
> This also requires jars etc. to have N&L files, which implies that the
> Maven artifacts also need to be reviewed.
>
> Voting on source releases is not an issue that is decided by PMCs; it
> is mandated by the ASF.
>
>> Oleg
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> For additional commands, e-mail: dev-help@hc.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
Sebb, there is a source release that we're voting on, so,
respectfully, i don't think this is an issue. I'm on the board and
infrastructure lists so have seen the discussion you mention. The key
point is that all ASF releases must include a source release and any
other binary artifacts are an optional convenience.
The issue with the Maven artifacts requiring source artifacts came
from projects that were doing pure Maven artifact only releases where
the jars in the Maven repository did not have an associated source
release so there was no way to recreate the Maven artifact jars from
the release. Thats not the case here as there is a source release and
building that creates all the Maven artifacts, so it does not matter
whether or not those individual Maven artifact jars themselves have
associated source artifacts.
I'm still +1 on this release.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 17:55 +0100, sebb wrote:
> > On 13/05/2010, ant elder <an...@gmail.com> wrote:
> > > On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
> > >
> > >
> > > >
> > > > This is actually quite easy, see
> > > > https://issues.apache.org/jira/browse/COMMONSSITE-55
> > > >
> > >
> > >
> > > Thanks for the pointer, i didn't know you could do use a file url in
> > > altDeploymentRepository.
> > >
> >
> > BTW, you can also add the profile to your local settings.xml.
> >
> > Though if many people may want to use the same method, it is more
> > efficient to add it to a shared resource such a a parent pom.
> >
>
>
> This approach results in corrupt / inconsistent maven metadata
> (maven-metadata.xml) unless the metadata is manually copied over.
>
This is what the Apache Nexus repo is for, see:
http://maven.apache.org/developers/release/apache-release.html
[As far as I can tell, one can use deploy to upload to the repo if one
does not use the release plugin.]
PMC then votes on the repo contents, which are then either promoted or dropped.
==
Note that I raised the issue of whether Maven sources need to be voted
on with the board/infrastructure.
All the responses say that Maven source packages need to be voted on
by the PMC, and this is supported by the updated releases FAQ at:
http://www.apache.org/dev/release.html
This also requires jars etc. to have N&L files, which implies that the
Maven artifacts also need to be reviewed.
Voting on source releases is not an issue that is decided by PMCs; it
is mandated by the ASF.
> Oleg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 17:55 +0100, sebb wrote:
> On 13/05/2010, ant elder <an...@gmail.com> wrote:
> > On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
> >
> >
> > >
> > > This is actually quite easy, see
> > > https://issues.apache.org/jira/browse/COMMONSSITE-55
> > >
> >
> >
> > Thanks for the pointer, i didn't know you could do use a file url in
> > altDeploymentRepository.
> >
>
> BTW, you can also add the profile to your local settings.xml.
>
> Though if many people may want to use the same method, it is more
> efficient to add it to a shared resource such a a parent pom.
>
This approach results in corrupt / inconsistent maven metadata
(maven-metadata.xml) unless the metadata is manually copied over.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, ant elder <an...@gmail.com> wrote:
> On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
>
>
> >
> > This is actually quite easy, see
> > https://issues.apache.org/jira/browse/COMMONSSITE-55
> >
>
>
> Thanks for the pointer, i didn't know you could do use a file url in
> altDeploymentRepository.
>
BTW, you can also add the profile to your local settings.xml.
Though if many people may want to use the same method, it is more
efficient to add it to a shared resource such a a parent pom.
> ...ant
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by ant elder <an...@gmail.com>.
On Thu, May 13, 2010 at 4:49 PM, sebb <se...@gmail.com> wrote:
>
> This is actually quite easy, see
> https://issues.apache.org/jira/browse/COMMONSSITE-55
>
Thanks for the pointer, i didn't know you could do use a file url in
altDeploymentRepository.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > > >
> > > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > > >
> > > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > > need to be voted on.
> > > > > >
> > > > >
> > > > >
> > > > > Sebastian, we have been through that, haven't we? Only source package
> > > > > represents an official release artifact that needs to be voted on.
> > > >
> > > > The Maven artifacts always include source files, either as source jars
> > > > (which should be provided), if not then at least pom.xml will be
> > > > included.
> > > >
> > > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > > ok, you should build them from source.
> > > >
> > > > That's not strictly true either - binary artifacts need to be
> > > > inspected to ensure that the appropriate N&L files are present.
> > > >
> > >
> > >
> > > Please see
> > > https://issues.apache.org/jira/browse/LEGAL-34
> > >
> >
> > Which was never really resolved and anyway does not cover the point
> > about N&L at all.
> >
>
>
> Precisely. Hen's statement boils down to a simple fact that there is no
> ASF wide policy on the matter and it is up to individual projects unless
> the Board rules otherwise.
>
>
> > >
> > > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > > are changing an established release process in the middle of a release
> > > > > without prior discussion and a consent from other committers.
> > > >
> > > > My point is that the process is IMO not following the ASF standard,
> > > > and therefore needs to be fixed.
> > > >
> > >
> > >
> > > There is no ASF standard. It is up to individual projects. Please see
> > > https://issues.apache.org/jira/browse/LEGAL-34
> >
> > Not really relevant as source releases must be approved by the PMC.
> > The Maven artefacts include source, and therefore must be voted on.
> >
>
>
> Is there an official statement to that effect by the Board I could have
> a look at?
>
No idea.
But I hope it's agreed that source releases must be voted on by the PMC.
Maven includes source, and is a release.
>
> > Regardless of the JIRA issue, I think the consumers of ASF releases
> > have a right to expect that the archives etc have been formally
> > approved as part of the "quality control" applied by the ASF
> > organisation.
> >
> > Why not just publish the Maven artefacts so we can include them in the vote?
> >
>
>
> How exactly do you suggest that I do that, as the artifacts are
> generated by Maven from source at deployment time?
This is actually quite easy, see
https://issues.apache.org/jira/browse/COMMONSSITE-55
> Besides, the release process is already is painful enough. I see no good
> reason for making it even more painful due to some completely arbitrary
> requirement.
It's not arbitrary.
> If you want Maven artifacts included in the release process, you should
> raise this matter with the PMC, and ideally not in the middle of a
> release.
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 15:51 +0100, sebb wrote:
> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > > >
> > > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > > >
> > > > > Should be largely a formality if the main packages are OK, but they do
> > > > > need to be voted on.
> > > > >
> > > >
> > > >
> > > > Sebastian, we have been through that, haven't we? Only source package
> > > > represents an official release artifact that needs to be voted on.
> > >
> > > The Maven artifacts always include source files, either as source jars
> > > (which should be provided), if not then at least pom.xml will be
> > > included.
> > >
> > > > Binary artifacts are merely byproducts. If you want to verify they are
> > > > ok, you should build them from source.
> > >
> > > That's not strictly true either - binary artifacts need to be
> > > inspected to ensure that the appropriate N&L files are present.
> > >
> >
> >
> > Please see
> > https://issues.apache.org/jira/browse/LEGAL-34
> >
>
> Which was never really resolved and anyway does not cover the point
> about N&L at all.
>
Precisely. Hen's statement boils down to a simple fact that there is no
ASF wide policy on the matter and it is up to individual projects unless
the Board rules otherwise.
> >
> > > > My main problem is not with uploading a bunch of files, but the fact you
> > > > are changing an established release process in the middle of a release
> > > > without prior discussion and a consent from other committers.
> > >
> > > My point is that the process is IMO not following the ASF standard,
> > > and therefore needs to be fixed.
> > >
> >
> >
> > There is no ASF standard. It is up to individual projects. Please see
> > https://issues.apache.org/jira/browse/LEGAL-34
>
> Not really relevant as source releases must be approved by the PMC.
> The Maven artefacts include source, and therefore must be voted on.
>
Is there an official statement to that effect by the Board I could have
a look at?
> Regardless of the JIRA issue, I think the consumers of ASF releases
> have a right to expect that the archives etc have been formally
> approved as part of the "quality control" applied by the ASF
> organisation.
>
> Why not just publish the Maven artefacts so we can include them in the vote?
>
How exactly do you suggest that I do that, as the artifacts are
generated by Maven from source at deployment time?
Besides, the release process is already is painful enough. I see no good
reason for making it even more painful due to some completely arbitrary
requirement.
If you want Maven artifacts included in the release process, you should
raise this matter with the PMC, and ideally not in the middle of a
release.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> > On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > > Please vote on releasing these packages as HttpComponents Client
> > > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > > >
> > > > Please can you upload the Maven packages as well, so we can vote on those too?
> > > >
> > > > Should be largely a formality if the main packages are OK, but they do
> > > > need to be voted on.
> > > >
> > >
> > >
> > > Sebastian, we have been through that, haven't we? Only source package
> > > represents an official release artifact that needs to be voted on.
> >
> > The Maven artifacts always include source files, either as source jars
> > (which should be provided), if not then at least pom.xml will be
> > included.
> >
> > > Binary artifacts are merely byproducts. If you want to verify they are
> > > ok, you should build them from source.
> >
> > That's not strictly true either - binary artifacts need to be
> > inspected to ensure that the appropriate N&L files are present.
> >
>
>
> Please see
> https://issues.apache.org/jira/browse/LEGAL-34
>
Which was never really resolved and anyway does not cover the point
about N&L at all.
>
> > > My main problem is not with uploading a bunch of files, but the fact you
> > > are changing an established release process in the middle of a release
> > > without prior discussion and a consent from other committers.
> >
> > My point is that the process is IMO not following the ASF standard,
> > and therefore needs to be fixed.
> >
>
>
> There is no ASF standard. It is up to individual projects. Please see
> https://issues.apache.org/jira/browse/LEGAL-34
Not really relevant as source releases must be approved by the PMC.
The Maven artefacts include source, and therefore must be voted on.
Regardless of the JIRA issue, I think the consumers of ASF releases
have a right to expect that the archives etc have been formally
approved as part of the "quality control" applied by the ASF
organisation.
Why not just publish the Maven artefacts so we can include them in the vote?
Only PMC-approved releases have the support of the ASF.
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 10:41 +0100, sebb wrote:
> On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > > Please vote on releasing these packages as HttpComponents Client
> > > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> > >
> > > Please can you upload the Maven packages as well, so we can vote on those too?
> > >
> > > Should be largely a formality if the main packages are OK, but they do
> > > need to be voted on.
> > >
> >
> >
> > Sebastian, we have been through that, haven't we? Only source package
> > represents an official release artifact that needs to be voted on.
>
> The Maven artifacts always include source files, either as source jars
> (which should be provided), if not then at least pom.xml will be
> included.
>
> > Binary artifacts are merely byproducts. If you want to verify they are
> > ok, you should build them from source.
>
> That's not strictly true either - binary artifacts need to be
> inspected to ensure that the appropriate N&L files are present.
>
Please see
https://issues.apache.org/jira/browse/LEGAL-34
> > My main problem is not with uploading a bunch of files, but the fact you
> > are changing an established release process in the middle of a release
> > without prior discussion and a consent from other committers.
>
> My point is that the process is IMO not following the ASF standard,
> and therefore needs to be fixed.
>
There is no ASF standard. It is up to individual projects. Please see
https://issues.apache.org/jira/browse/LEGAL-34
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > Please vote on releasing these packages as HttpComponents Client
> > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> >
> > Please can you upload the Maven packages as well, so we can vote on those too?
> >
> > Should be largely a formality if the main packages are OK, but they do
> > need to be voted on.
> >
>
>
> Sebastian, we have been through that, haven't we? Only source package
> represents an official release artifact that needs to be voted on.
The Maven artifacts always include source files, either as source jars
(which should be provided), if not then at least pom.xml will be
included.
> Binary artifacts are merely byproducts. If you want to verify they are
> ok, you should build them from source.
That's not strictly true either - binary artifacts need to be
inspected to ensure that the appropriate N&L files are present.
> My main problem is not with uploading a bunch of files, but the fact you
> are changing an established release process in the middle of a release
> without prior discussion and a consent from other committers.
My point is that the process is IMO not following the ASF standard,
and therefore needs to be fixed.
>
> Oleg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 01:12 +0100, sebb wrote:
> On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > Please vote on releasing these packages as HttpComponents Client
> > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
>
> Please can you upload the Maven packages as well, so we can vote on those too?
>
> Should be largely a formality if the main packages are OK, but they do
> need to be voted on.
>
Sebastian, we have been through that, haven't we? Only source package
represents an official release artifact that needs to be voted on.
Binary artifacts are merely byproducts. If you want to verify they are
ok, you should build them from source.
My main problem is not with uploading a bunch of files, but the fact you
are changing an established release process in the middle of a release
without prior discussion and a consent from other committers.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2010-05-13 at 01:44 +0100, sebb wrote:
> On 13/05/2010, sebb <se...@gmail.com> wrote:
> > On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > Please vote on releasing these packages as HttpComponents Client
> > > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
> >
> >
> > Please can you upload the Maven packages as well, so we can vote on those too?
> >
> > Should be largely a formality if the main packages are OK, but they do
> > need to be voted on.
> >
> >
> > > Release notes:
> > > http://people.apache.org/~olegk/httpclient-4.1-alpha2/RELEASE_NOTES.txt
> > >
> > > Release tag:
> > > http://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.1-alpha2/
>
> Sorry, but -1 as the archives don't agree with the SVN tag - two
> source files are different.
>
> These were the files I fixed to add the final qualifiers (needed as
> the class is tagged @Immutable).
>
> Were the archives created from the SVN tag?
>
> The tag appears to be up to date, but the archives are not, so I don't
> know what has happened.
>
> Note: there were also a lot of eol-style settings missing, which I
> have fixed in trunk, but of course the tag is now out of date.
>
I'll re-tag the release, rebuild the packages and restart the vote.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 13/05/2010, sebb <se...@gmail.com> wrote:
> On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> > Please vote on releasing these packages as HttpComponents Client
> > 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
>
>
> Please can you upload the Maven packages as well, so we can vote on those too?
>
> Should be largely a formality if the main packages are OK, but they do
> need to be voted on.
>
>
> > Release notes:
> > http://people.apache.org/~olegk/httpclient-4.1-alpha2/RELEASE_NOTES.txt
> >
> > Release tag:
> > http://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.1-alpha2/
Sorry, but -1 as the archives don't agree with the SVN tag - two
source files are different.
These were the files I fixed to add the final qualifiers (needed as
the class is tagged @Immutable).
Were the archives created from the SVN tag?
The tag appears to be up to date, but the archives are not, so I don't
know what has happened.
Note: there were also a lot of eol-style settings missing, which I
have fixed in trunk, but of course the tag is now out of date.
> >
> > --------------------------------------------------------------------------
> > Vote: HttpComponents Client 4.1-alpha2 release
> > [ ] +1 Release the packages as HttpComponents Client 4.1-alpha2.
> > [ ] -1 I am against releasing the packages (must include a reason).
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> > For additional commands, e-mail: dev-help@hc.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by sebb <se...@gmail.com>.
On 12/05/2010, Oleg Kalnichevski <ol...@apache.org> wrote:
> Please vote on releasing these packages as HttpComponents Client
> 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
Please can you upload the Maven packages as well, so we can vote on those too?
Should be largely a formality if the main packages are OK, but they do
need to be voted on.
> Release notes:
> http://people.apache.org/~olegk/httpclient-4.1-alpha2/RELEASE_NOTES.txt
>
> Release tag:
> http://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.1-alpha2/
>
> --------------------------------------------------------------------------
> Vote: HttpComponents Client 4.1-alpha2 release
> [ ] +1 Release the packages as HttpComponents Client 4.1-alpha2.
> [ ] -1 I am against releasing the packages (must include a reason).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: [VOTE] HttpComponents Client 4.1-alpha2 release
Posted by Oleg Kalnichevski <ol...@apache.org>.
[x] +1 Release the packages as HttpComponents Client 4.1-alpha2
On Wed, 2010-05-12 at 23:53 +0200, Oleg Kalnichevski wrote:
> Please vote on releasing these packages as HttpComponents Client
> 4.1-alpha2. The vote is open for the next 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/httpclient-4.1-alpha2/
>
> Release notes:
> http://people.apache.org/~olegk/httpclient-4.1-alpha2/RELEASE_NOTES.txt
>
> Release tag:
> http://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.1-alpha2/
>
> --------------------------------------------------------------------------
> Vote: HttpComponents Client 4.1-alpha2 release
> [ ] +1 Release the packages as HttpComponents Client 4.1-alpha2.
> [ ] -1 I am against releasing the packages (must include a reason).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org