You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Andrew Bayer <an...@gmail.com> on 2013/06/13 03:35:18 UTC
[VOTE] Release Apache jclouds 1.6.1-incubating RC3
Hello,
This is the third release candidate for Apache jclouds 1.6.1-incubating,
the first jclouds release at Apache.
This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
*** Please download, test and vote by Saturday, June 15th, 7pm PDT.
Note that we are voting upon the source (tag), binaries are provided for
convenience.
Source and binary files:
http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachejclouds-016
The tags to be voted upon:
- jclouds -
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
- jclouds-labs -
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
- jclouds-chef -
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
- jclouds-karaf -
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
- jclouds-cli -
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
jclouds KEYS file containing PGP keys we use to sign the release:
http://www.apache.org/dist/incubator/jclouds/KEYS
[ ] +1
[ ] 0
[ ] -1 (explain why)
A.
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
Release doc incoming once we actually have the finished released. =)
A.
On Sun, Jun 16, 2013 at 7:34 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jun 16, 2013 at 9:36 PM, Everett Toews
> <ev...@rackspace.com> wrote:
> > Hi Igansi,
> >
> > I'd like to get more familiar with the build/release process. Do you
> mind answering a number of questions below?
> >
>
> Honestly - this process probably needs to be documented:
> CloudStack's variant of this page is here:
> https://cwiki.apache.org/CLOUDSTACK/release-test-procedure.html
>
> > On Jun 15, 2013, at 5:37 PM, Ignasi wrote:
> >
> >> I built the tags and all builds succeeded (the build included RAT
> >> plugin execution and everything is ok too).
> >
> > How did you build from the tags?
> >
> > Anything special needed to run the RAT plugin?
> >
>
> Nah, Maven takes care of it all.
>
>
> >> Run the live tests for Chef and Hosted Chef. All passing except one in
> >> HostedChef due to a known issue in HostedChef, so everything is OK in
> >> our side.
> >> Also verified the signatures and checksums of the downloaded artifacts
> >> from the staging repo and the source distribution tar balls with
> >> Andrew's key in the jclouds KEYS file and the one in the commiters
> >> directory and they are OK.
> >
> > How did you do these steps?
> >
> > Where does that KEYS file live?
> >
> > Regards,
> > Everett
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by David Nalley <da...@gnsa.us>.
On Sun, Jun 16, 2013 at 9:36 PM, Everett Toews
<ev...@rackspace.com> wrote:
> Hi Igansi,
>
> I'd like to get more familiar with the build/release process. Do you mind answering a number of questions below?
>
Honestly - this process probably needs to be documented:
CloudStack's variant of this page is here:
https://cwiki.apache.org/CLOUDSTACK/release-test-procedure.html
> On Jun 15, 2013, at 5:37 PM, Ignasi wrote:
>
>> I built the tags and all builds succeeded (the build included RAT
>> plugin execution and everything is ok too).
>
> How did you build from the tags?
>
> Anything special needed to run the RAT plugin?
>
Nah, Maven takes care of it all.
>> Run the live tests for Chef and Hosted Chef. All passing except one in
>> HostedChef due to a known issue in HostedChef, so everything is OK in
>> our side.
>> Also verified the signatures and checksums of the downloaded artifacts
>> from the staging repo and the source distribution tar balls with
>> Andrew's key in the jclouds KEYS file and the one in the commiters
>> directory and they are OK.
>
> How did you do these steps?
>
> Where does that KEYS file live?
>
> Regards,
> Everett
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Everett Toews <ev...@RACKSPACE.COM>.
Hi Igansi,
I'd like to get more familiar with the build/release process. Do you mind answering a number of questions below?
On Jun 15, 2013, at 5:37 PM, Ignasi wrote:
> I built the tags and all builds succeeded (the build included RAT
> plugin execution and everything is ok too).
How did you build from the tags?
Anything special needed to run the RAT plugin?
> Run the live tests for Chef and Hosted Chef. All passing except one in
> HostedChef due to a known issue in HostedChef, so everything is OK in
> our side.
> Also verified the signatures and checksums of the downloaded artifacts
> from the staging repo and the source distribution tar balls with
> Andrew's key in the jclouds KEYS file and the one in the commiters
> directory and they are OK.
How did you do these steps?
Where does that KEYS file live?
Regards,
Everett
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Ignasi <ig...@gmail.com>.
I built the tags and all builds succeeded (the build included RAT
plugin execution and everything is ok too).
Run the live tests for Chef and Hosted Chef. All passing except one in
HostedChef due to a known issue in HostedChef, so everything is OK in
our side.
Also verified the signatures and checksums of the downloaded artifacts
from the staging repo and the source distribution tar balls with
Andrew's key in the jclouds KEYS file and the one in the commiters
directory and they are OK.
+1 binding, PPMC.
On 15 June 2013 23:39, David Nalley <da...@gnsa.us> wrote:
> On Wed, Jun 12, 2013 at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>> Hello,
>>
>> This is the third release candidate for Apache jclouds 1.6.1-incubating,
>> the first jclouds release at Apache.
>>
>> This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
>>
>> It fixes the following issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>>
>> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>>
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>>
>> Source and binary files:
>> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachejclouds-016
>>
>> The tags to be voted upon:
>> - jclouds -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
>> - jclouds-labs -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
>> - jclouds-chef -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
>> - jclouds-karaf -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
>> - jclouds-cli -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>>
>> jclouds KEYS file containing PGP keys we use to sign the release:
>> http://www.apache.org/dist/incubator/jclouds/KEYS
>>
>> [ ] +1
>> [ ] 0
>> [ ] -1 (explain why)
>>
>> A.
>
>
>
> +1 (binding)
> I checked both checksums, gpg sigs. (It'd be nice to get you tighter
> into the ASF web of trust abayer).
> I ran rat, looked at the 'non-licensed' output, which seems largely
> test expectations, which isn't inherently copyrightable in the first
> place.
> DISCLAIMER is in place on the release artifacts. NOTICE and LICENSE
> appear to be in good shape.
> I compared tarballs against the git tags.
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
Yeah, not sure how to get NOTICE to contain the dependencies - doesn't look
like the remote resources stuff in org.apache:apache does that.
A.
On Sun, Jun 16, 2013 at 2:22 AM, Olivier Lamy <ol...@apache.org> wrote:
> Something maybe someone will complain on general incubator@ is the
> content of NOTICE file in
> jclouds-cli-assembly-1.6.1-incubating.zip/tar.gz
> It doesn't contain reference to others included binaries with ASF
> license (as guava etc).
> but IANAL and that's in DEPENDENCIES.
> So +1 (IPMC binding) for me.
>
> 2013/6/16 Andrew Bayer <an...@gmail.com>:
> > On Jun 15, 2013, at 2:39 PM, David Nalley <da...@gnsa.us> wrote:
> >
> >> I checked both checksums, gpg sigs. (It'd be nice to get you tighter
> >> into the ASF web of trust abayer).
> >
> > Yeah, I keep forgetting to keysign with coworkers in the web of trust -
> I promise I will soon!
> >
> > A.
> >
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
Just the binary archives, yeah - the source bits are still there, and the
RC is otherwise unchanged.
A.
On Sun, Jun 16, 2013 at 3:55 PM, Suresh Marru <sm...@apache.org> wrote:
> On Jun 16, 2013, at 12:12 PM, Andrew Bayer <an...@gmail.com> wrote:
>
> > I'll yank it, then.
>
> Hi Andrew,
>
> Thanks for your persistence with the release, just to clarify are you just
> yanking the jclouds-cli-assembly-1.6.1-incubating* or working on a new RC?
> I am in the middle of my review and so far only have non-blocking
> suggestions. Will post notes and vote in the next couple of hours.
>
> Suresh
>
>
> >
> > A.
> >
> > On Sun, Jun 16, 2013 at 9:08 AM, David Nalley <da...@gnsa.us> wrote:
> >
> >> On Sun, Jun 16, 2013 at 5:22 AM, Olivier Lamy <ol...@apache.org> wrote:
> >>> Something maybe someone will complain on general incubator@ is the
> >>> content of NOTICE file in
> >>> jclouds-cli-assembly-1.6.1-incubating.zip/tar.gz
> >>> It doesn't contain reference to others included binaries with ASF
> >>> license (as guava etc).
> >>> but IANAL and that's in DEPENDENCIES.
> >>> So +1 (IPMC binding) for me.
> >>>
> >>
> >>
> >> Yeah, I agree with Olivier.
> >> I purposefully did not review -assembly as it's a binary, and thus not
> >> part of your release. I really think that combining a convenience
> >> binary in the same place as the release artifacts is just inviting
> >> confusion and more places to receive criticism, especially while you
> >> are in the incubator. Again - it's not a release artifact, but no need
> >> to cloud the issue.
> >>
> >> --David
> >>
>
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Suresh Marru <sm...@apache.org>.
On Jun 16, 2013, at 12:12 PM, Andrew Bayer <an...@gmail.com> wrote:
> I'll yank it, then.
Hi Andrew,
Thanks for your persistence with the release, just to clarify are you just yanking the jclouds-cli-assembly-1.6.1-incubating* or working on a new RC? I am in the middle of my review and so far only have non-blocking suggestions. Will post notes and vote in the next couple of hours.
Suresh
>
> A.
>
> On Sun, Jun 16, 2013 at 9:08 AM, David Nalley <da...@gnsa.us> wrote:
>
>> On Sun, Jun 16, 2013 at 5:22 AM, Olivier Lamy <ol...@apache.org> wrote:
>>> Something maybe someone will complain on general incubator@ is the
>>> content of NOTICE file in
>>> jclouds-cli-assembly-1.6.1-incubating.zip/tar.gz
>>> It doesn't contain reference to others included binaries with ASF
>>> license (as guava etc).
>>> but IANAL and that's in DEPENDENCIES.
>>> So +1 (IPMC binding) for me.
>>>
>>
>>
>> Yeah, I agree with Olivier.
>> I purposefully did not review -assembly as it's a binary, and thus not
>> part of your release. I really think that combining a convenience
>> binary in the same place as the release artifacts is just inviting
>> confusion and more places to receive criticism, especially while you
>> are in the incubator. Again - it's not a release artifact, but no need
>> to cloud the issue.
>>
>> --David
>>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
I'll yank it, then.
A.
On Sun, Jun 16, 2013 at 9:08 AM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jun 16, 2013 at 5:22 AM, Olivier Lamy <ol...@apache.org> wrote:
> > Something maybe someone will complain on general incubator@ is the
> > content of NOTICE file in
> > jclouds-cli-assembly-1.6.1-incubating.zip/tar.gz
> > It doesn't contain reference to others included binaries with ASF
> > license (as guava etc).
> > but IANAL and that's in DEPENDENCIES.
> > So +1 (IPMC binding) for me.
> >
>
>
> Yeah, I agree with Olivier.
> I purposefully did not review -assembly as it's a binary, and thus not
> part of your release. I really think that combining a convenience
> binary in the same place as the release artifacts is just inviting
> confusion and more places to receive criticism, especially while you
> are in the incubator. Again - it's not a release artifact, but no need
> to cloud the issue.
>
> --David
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by David Nalley <da...@gnsa.us>.
On Sun, Jun 16, 2013 at 5:22 AM, Olivier Lamy <ol...@apache.org> wrote:
> Something maybe someone will complain on general incubator@ is the
> content of NOTICE file in
> jclouds-cli-assembly-1.6.1-incubating.zip/tar.gz
> It doesn't contain reference to others included binaries with ASF
> license (as guava etc).
> but IANAL and that's in DEPENDENCIES.
> So +1 (IPMC binding) for me.
>
Yeah, I agree with Olivier.
I purposefully did not review -assembly as it's a binary, and thus not
part of your release. I really think that combining a convenience
binary in the same place as the release artifacts is just inviting
confusion and more places to receive criticism, especially while you
are in the incubator. Again - it's not a release artifact, but no need
to cloud the issue.
--David
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Olivier Lamy <ol...@apache.org>.
Something maybe someone will complain on general incubator@ is the
content of NOTICE file in
jclouds-cli-assembly-1.6.1-incubating.zip/tar.gz
It doesn't contain reference to others included binaries with ASF
license (as guava etc).
but IANAL and that's in DEPENDENCIES.
So +1 (IPMC binding) for me.
2013/6/16 Andrew Bayer <an...@gmail.com>:
> On Jun 15, 2013, at 2:39 PM, David Nalley <da...@gnsa.us> wrote:
>
>> I checked both checksums, gpg sigs. (It'd be nice to get you tighter
>> into the ASF web of trust abayer).
>
> Yeah, I keep forgetting to keysign with coworkers in the web of trust - I promise I will soon!
>
> A.
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
On Jun 15, 2013, at 2:39 PM, David Nalley <da...@gnsa.us> wrote:
> I checked both checksums, gpg sigs. (It'd be nice to get you tighter
> into the ASF web of trust abayer).
Yeah, I keep forgetting to keysign with coworkers in the web of trust - I promise I will soon!
A.
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by David Nalley <da...@gnsa.us>.
On Wed, Jun 12, 2013 at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
> Hello,
>
> This is the third release candidate for Apache jclouds 1.6.1-incubating,
> the first jclouds release at Apache.
>
> This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>
> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachejclouds-016
>
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
>
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
>
> A.
+1 (binding)
I checked both checksums, gpg sigs. (It'd be nice to get you tighter
into the ASF web of trust abayer).
I ran rat, looked at the 'non-licensed' output, which seems largely
test expectations, which isn't inherently copyrightable in the first
place.
DISCLAIMER is in place on the release artifacts. NOTICE and LICENSE
appear to be in good shape.
I compared tarballs against the git tags.
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Suresh Marru <sm...@apache.org>.
On Jun 17, 2013, at 6:22 PM, Andrew Bayer <an...@gmail.com> wrote:
> Suresh, while I'm thinking of it (and working on
> https://wiki.apache.org/jclouds/Releasing%20jclouds) - how does one use
> https://dist.apache.org/repos/dist/dev/incubator/jclouds/ anyway? I'm not
> sure things can get there in the first place…
Hi Andrew,
This is the svn location. So you checkout this location, create a $version/$RC-X directory and add the artifacts and commit. I am not sure if there is a git equivalent space.
Suresh
>
> A.
>
> On Sun, Jun 16, 2013 at 5:46 PM, Suresh Marru <sm...@apache.org> wrote:
>
>> Great progress Andrew with the release artifacts. I am in email catch up
>> mode and might have missed some discussion. So I will post some discussions
>> first, will hold vote for now pending this discussion. If these issues have
>> been discussed previously I will vote. Meanwhile, I will keep looking.
>>
>> The signatures all look good, maven builds of all sources success, the
>> nexus repo is correctly populated (see improvements below), with required
>> NOTICE, LICENSE and DISCLAIMER files.
>>
>> I am personally not sure "Copyright 2013 jclouds" is a blocker or not. The
>> instructions clearly say it has to be Apache $Project -
>> http://www.apache.org/legal/src-headers.html#notice
>>
>> I will not gate this and will vote positively, since the following line
>> clearly says the software is developed at ASF, but I will rely on other
>> mentor/IPMC opinion on this.
>>
>> The NOTICE.txt file in previous iterations (example:
>> https://repository.apache.org/content/repositories/orgapachejclouds-015/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar)
>> has significant dependency notices. Why did these notices did not get
>> populated into the current NOTICE file (example -
>> https://repository.apache.org/content/repositories/orgapachejclouds-016/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar
>> )
>>
>> Here are some non-blocking comments and suggestions for future
>> improvements:
>>
>> * Please instruct the release vote discussion to [VOTE] and [DISCUSS]
>> threads. As soon as you post the [VOTE] thread, immediately post a
>> [DISCUSS] email and encourage all review and discussions to discuss thread.
>> The vote thread is advised to only have votes. Quick reference examples
>> [1], [2]
>> * Please try to post the release artifacts to official dev distribution
>> area [3] instead of your personal space - (Note the *dev*, this location
>> is not mirrored, the *release* area [4] will be).
>> * Fix the NOTICE file from jclouds to Apache jclouds
>> * Include Project metadata in the parent pom - Mailing List, Issue
>> Management, Developers. Example if needed [5].
>> * As David already pointed out, try and have atleast 3 apache committers
>> sign your key.
>> * I would drop all the cancelled RC nexus repo's before pushing new RC's.
>> Currently you will see 7 staging repos -
>> https://repository.apache.org/index.html#stagingRepositories. Except the
>> orgapachejclouds-016, please drop others.
>>
>> Suresh
>> [1] - http://airavata.apache.org/development/release-vote.txt
>> [2] - http://airavata.apache.org/development/release-discuss.txt
>> [3] - https://dist.apache.org/repos/dist/dev/incubator/jclouds/
>> [4] - https://dist.apache.org/repos/dist/release/incubator/jclouds/
>> [5] - https://svn.apache.org/repos/asf/airavata/trunk/pom.xml
>>
>> On Jun 12, 2013, at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> This is the third release candidate for Apache jclouds 1.6.1-incubating,
>>> the first jclouds release at Apache.
>>>
>>> This is a PPMC vote - if this passes, we'll move it onward to an IPMC
>> vote.
>>>
>>> It fixes the following issues:
>>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>>>
>>> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>>>
>>> Note that we are voting upon the source (tag), binaries are provided for
>>> convenience.
>>>
>>> Source and binary files:
>>> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>>>
>>> Maven staging repo:
>>> https://repository.apache.org/content/repositories/orgapachejclouds-016
>>>
>>> The tags to be voted upon:
>>> - jclouds -
>>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
>>> - jclouds-labs -
>>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
>>> - jclouds-chef -
>>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
>>> - jclouds-karaf -
>>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
>>> - jclouds-cli -
>>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>>>
>>> jclouds KEYS file containing PGP keys we use to sign the release:
>>> http://www.apache.org/dist/incubator/jclouds/KEYS
>>>
>>> [ ] +1
>>> [ ] 0
>>> [ ] -1 (explain why)
>>>
>>> A.
>>
>>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
Suresh, while I'm thinking of it (and working on
https://wiki.apache.org/jclouds/Releasing%20jclouds) - how does one use
https://dist.apache.org/repos/dist/dev/incubator/jclouds/ anyway? I'm not
sure things can get there in the first place...
A.
On Sun, Jun 16, 2013 at 5:46 PM, Suresh Marru <sm...@apache.org> wrote:
> Great progress Andrew with the release artifacts. I am in email catch up
> mode and might have missed some discussion. So I will post some discussions
> first, will hold vote for now pending this discussion. If these issues have
> been discussed previously I will vote. Meanwhile, I will keep looking.
>
> The signatures all look good, maven builds of all sources success, the
> nexus repo is correctly populated (see improvements below), with required
> NOTICE, LICENSE and DISCLAIMER files.
>
> I am personally not sure "Copyright 2013 jclouds" is a blocker or not. The
> instructions clearly say it has to be Apache $Project -
> http://www.apache.org/legal/src-headers.html#notice
>
> I will not gate this and will vote positively, since the following line
> clearly says the software is developed at ASF, but I will rely on other
> mentor/IPMC opinion on this.
>
> The NOTICE.txt file in previous iterations (example:
> https://repository.apache.org/content/repositories/orgapachejclouds-015/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar)
> has significant dependency notices. Why did these notices did not get
> populated into the current NOTICE file (example -
> https://repository.apache.org/content/repositories/orgapachejclouds-016/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar
> )
>
> Here are some non-blocking comments and suggestions for future
> improvements:
>
> * Please instruct the release vote discussion to [VOTE] and [DISCUSS]
> threads. As soon as you post the [VOTE] thread, immediately post a
> [DISCUSS] email and encourage all review and discussions to discuss thread.
> The vote thread is advised to only have votes. Quick reference examples
> [1], [2]
> * Please try to post the release artifacts to official dev distribution
> area [3] instead of your personal space - (Note the *dev*, this location
> is not mirrored, the *release* area [4] will be).
> * Fix the NOTICE file from jclouds to Apache jclouds
> * Include Project metadata in the parent pom - Mailing List, Issue
> Management, Developers. Example if needed [5].
> * As David already pointed out, try and have atleast 3 apache committers
> sign your key.
> * I would drop all the cancelled RC nexus repo's before pushing new RC's.
> Currently you will see 7 staging repos -
> https://repository.apache.org/index.html#stagingRepositories. Except the
> orgapachejclouds-016, please drop others.
>
> Suresh
> [1] - http://airavata.apache.org/development/release-vote.txt
> [2] - http://airavata.apache.org/development/release-discuss.txt
> [3] - https://dist.apache.org/repos/dist/dev/incubator/jclouds/
> [4] - https://dist.apache.org/repos/dist/release/incubator/jclouds/
> [5] - https://svn.apache.org/repos/asf/airavata/trunk/pom.xml
>
> On Jun 12, 2013, at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>
> > Hello,
> >
> > This is the third release candidate for Apache jclouds 1.6.1-incubating,
> > the first jclouds release at Apache.
> >
> > This is a PPMC vote - if this passes, we'll move it onward to an IPMC
> vote.
> >
> > It fixes the following issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
> >
> > *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachejclouds-016
> >
> > The tags to be voted upon:
> > - jclouds -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
> > - jclouds-labs -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
> > - jclouds-chef -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
> > - jclouds-karaf -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
> > - jclouds-cli -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
> >
> > jclouds KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/incubator/jclouds/KEYS
> >
> > [ ] +1
> > [ ] 0
> > [ ] -1 (explain why)
> >
> > A.
>
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Suresh Marru <sm...@apache.org>.
+ 1 (IPMC Binding).
I have trying to poke more into the release artifacts. I am a little concerned with NOTICE file populating inside the jars, but I will need to spend more time to raise concrete concerns. Since so far all the aspects I reviewed are good, I am voting + 1. Lets see whats others have to say on the general list. For next release, I will engage early on and will help with L, N files.
Good job over all,
Suresh
On Jun 16, 2013, at 8:46 PM, Suresh Marru <sm...@apache.org> wrote:
> Great progress Andrew with the release artifacts. I am in email catch up mode and might have missed some discussion. So I will post some discussions first, will hold vote for now pending this discussion. If these issues have been discussed previously I will vote. Meanwhile, I will keep looking.
>
> The signatures all look good, maven builds of all sources success, the nexus repo is correctly populated (see improvements below), with required NOTICE, LICENSE and DISCLAIMER files.
>
> I am personally not sure "Copyright 2013 jclouds" is a blocker or not. The instructions clearly say it has to be Apache $Project - http://www.apache.org/legal/src-headers.html#notice
>
> I will not gate this and will vote positively, since the following line clearly says the software is developed at ASF, but I will rely on other mentor/IPMC opinion on this.
>
> The NOTICE.txt file in previous iterations (example: https://repository.apache.org/content/repositories/orgapachejclouds-015/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar) has significant dependency notices. Why did these notices did not get populated into the current NOTICE file (example - https://repository.apache.org/content/repositories/orgapachejclouds-016/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar)
>
> Here are some non-blocking comments and suggestions for future improvements:
>
> * Please instruct the release vote discussion to [VOTE] and [DISCUSS] threads. As soon as you post the [VOTE] thread, immediately post a [DISCUSS] email and encourage all review and discussions to discuss thread. The vote thread is advised to only have votes. Quick reference examples [1], [2]
> * Please try to post the release artifacts to official dev distribution area [3] instead of your personal space - (Note the *dev*, this location is not mirrored, the *release* area [4] will be).
> * Fix the NOTICE file from jclouds to Apache jclouds
> * Include Project metadata in the parent pom - Mailing List, Issue Management, Developers. Example if needed [5].
> * As David already pointed out, try and have atleast 3 apache committers sign your key.
> * I would drop all the cancelled RC nexus repo's before pushing new RC's. Currently you will see 7 staging repos - https://repository.apache.org/index.html#stagingRepositories. Except the orgapachejclouds-016, please drop others.
>
> Suresh
> [1] - http://airavata.apache.org/development/release-vote.txt
> [2] - http://airavata.apache.org/development/release-discuss.txt
> [3] - https://dist.apache.org/repos/dist/dev/incubator/jclouds/
> [4] - https://dist.apache.org/repos/dist/release/incubator/jclouds/
> [5] - https://svn.apache.org/repos/asf/airavata/trunk/pom.xml
>
> On Jun 12, 2013, at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>
>> Hello,
>>
>> This is the third release candidate for Apache jclouds 1.6.1-incubating,
>> the first jclouds release at Apache.
>>
>> This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
>>
>> It fixes the following issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>>
>> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>>
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>>
>> Source and binary files:
>> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachejclouds-016
>>
>> The tags to be voted upon:
>> - jclouds -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
>> - jclouds-labs -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
>> - jclouds-chef -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
>> - jclouds-karaf -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
>> - jclouds-cli -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>>
>> jclouds KEYS file containing PGP keys we use to sign the release:
>> http://www.apache.org/dist/incubator/jclouds/KEYS
>>
>> [ ] +1
>> [ ] 0
>> [ ] -1 (explain why)
>>
>> A.
>
[RESULT] [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
The vote is now closed, and with 5 +1s, 3 from mentors, we're ready to go
to the IPMC. Thanks, all!
A.
On Sun, Jun 16, 2013 at 6:45 PM, Andrew Bayer <an...@gmail.com>wrote:
> The "Copyright 2013 jclouds" thing is easily fixed - that's just taken
> from the name of the top-level POM. I'll fix that for all future releases.
>
> in re: NOTICE - so this is, at its core, a difference between how we had
> been doing it and how the Apache super-parent POM does it. The standard
> Apache NOTICE doesn't have dependencies in it; instead, it's got a separate
> DEPENDENCIES file - see
> https://svn.apache.org/repos/asf/maven/resources/tags/apache-jar-resource-bundle-1.4/src/main/resources/META-INF/DEPENDENCIES.vmand
> https://svn.apache.org/repos/asf/maven/resources/tags/apache-jar-resource-bundle-1.4/src/main/resources/META-INF/NOTICE.vm
> .
>
> And the staging repos are dropped - I forgot. =)
>
> A.
>
>
> On Sun, Jun 16, 2013 at 5:46 PM, Suresh Marru <sm...@apache.org> wrote:
>
>> Great progress Andrew with the release artifacts. I am in email catch up
>> mode and might have missed some discussion. So I will post some discussions
>> first, will hold vote for now pending this discussion. If these issues have
>> been discussed previously I will vote. Meanwhile, I will keep looking.
>>
>> The signatures all look good, maven builds of all sources success, the
>> nexus repo is correctly populated (see improvements below), with required
>> NOTICE, LICENSE and DISCLAIMER files.
>>
>> I am personally not sure "Copyright 2013 jclouds" is a blocker or not.
>> The instructions clearly say it has to be Apache $Project -
>> http://www.apache.org/legal/src-headers.html#notice
>>
>> I will not gate this and will vote positively, since the following line
>> clearly says the software is developed at ASF, but I will rely on other
>> mentor/IPMC opinion on this.
>>
>> The NOTICE.txt file in previous iterations (example:
>> https://repository.apache.org/content/repositories/orgapachejclouds-015/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar)
>> has significant dependency notices. Why did these notices did not get
>> populated into the current NOTICE file (example -
>> https://repository.apache.org/content/repositories/orgapachejclouds-016/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar
>> )
>>
>> Here are some non-blocking comments and suggestions for future
>> improvements:
>>
>> * Please instruct the release vote discussion to [VOTE] and [DISCUSS]
>> threads. As soon as you post the [VOTE] thread, immediately post a
>> [DISCUSS] email and encourage all review and discussions to discuss thread.
>> The vote thread is advised to only have votes. Quick reference examples
>> [1], [2]
>> * Please try to post the release artifacts to official dev distribution
>> area [3] instead of your personal space - (Note the *dev*, this location
>> is not mirrored, the *release* area [4] will be).
>> * Fix the NOTICE file from jclouds to Apache jclouds
>> * Include Project metadata in the parent pom - Mailing List, Issue
>> Management, Developers. Example if needed [5].
>> * As David already pointed out, try and have atleast 3 apache committers
>> sign your key.
>> * I would drop all the cancelled RC nexus repo's before pushing new RC's.
>> Currently you will see 7 staging repos -
>> https://repository.apache.org/index.html#stagingRepositories. Except the
>> orgapachejclouds-016, please drop others.
>>
>> Suresh
>> [1] - http://airavata.apache.org/development/release-vote.txt
>> [2] - http://airavata.apache.org/development/release-discuss.txt
>> [3] - https://dist.apache.org/repos/dist/dev/incubator/jclouds/
>> [4] - https://dist.apache.org/repos/dist/release/incubator/jclouds/
>> [5] - https://svn.apache.org/repos/asf/airavata/trunk/pom.xml
>>
>> On Jun 12, 2013, at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>>
>> > Hello,
>> >
>> > This is the third release candidate for Apache jclouds 1.6.1-incubating,
>> > the first jclouds release at Apache.
>> >
>> > This is a PPMC vote - if this passes, we'll move it onward to an IPMC
>> vote.
>> >
>> > It fixes the following issues:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>> >
>> > *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>> >
>> > Note that we are voting upon the source (tag), binaries are provided for
>> > convenience.
>> >
>> > Source and binary files:
>> > http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>> >
>> > Maven staging repo:
>> > https://repository.apache.org/content/repositories/orgapachejclouds-016
>> >
>> > The tags to be voted upon:
>> > - jclouds -
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
>> > - jclouds-labs -
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
>> > - jclouds-chef -
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
>> > - jclouds-karaf -
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
>> > - jclouds-cli -
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>> >
>> > jclouds KEYS file containing PGP keys we use to sign the release:
>> > http://www.apache.org/dist/incubator/jclouds/KEYS
>> >
>> > [ ] +1
>> > [ ] 0
>> > [ ] -1 (explain why)
>> >
>> > A.
>>
>>
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
Fix is ready to go - I'm making sure that the project names in each
top-level POM start with "Apache jclouds" (which fixes all the generated
NOTICEs), I nuked the resources/{LICENSE,NOTICE}.txt files in both
incubator-jclouds.git and incubator-jclouds-chef.git, and updated the
README.mds. Pushing it now.
A.
On Sun, Jun 16, 2013 at 7:31 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jun 16, 2013 at 10:24 PM, Andrew Bayer <an...@gmail.com>
> wrote:
> > Argh. Of course this pops up right after I start the general@ vote
> > thread... =)
> >
> > Should I drop that vote, fix this, and run a new vote here?
> >
> > A.
>
> First, fix the problem.
>
> I personally wouldn't stop the vote now - you've got 3 +1s from IPMC
> members, and none of us have yet changed our vote, if you get pushback
> from other mentors or IPMC members, deal with it as it comes. I
> personally don't see this as a blocker, particularly if its already
> been fixed and will be remedied in the next release. Just a few more
> pieces that need cleanup that were missed.
>
> --David
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Suresh Marru <sm...@apache.org>.
On Jun 16, 2013, at 10:31 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jun 16, 2013 at 10:24 PM, Andrew Bayer <an...@gmail.com> wrote:
>> Argh. Of course this pops up right after I start the general@ vote
>> thread... =)
>>
>> Should I drop that vote, fix this, and run a new vote here?
>>
>> A.
>
> First, fix the problem.
>
> I personally wouldn't stop the vote now - you've got 3 +1s from IPMC
> members, and none of us have yet changed our vote, if you get pushback
> from other mentors or IPMC members, deal with it as it comes. I
> personally don't see this as a blocker, particularly if its already
> been fixed and will be remedied in the next release. Just a few more
> pieces that need cleanup that were missed.
Agreed.
Suresh
>
> --David
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by David Nalley <da...@gnsa.us>.
On Sun, Jun 16, 2013 at 10:24 PM, Andrew Bayer <an...@gmail.com> wrote:
> Argh. Of course this pops up right after I start the general@ vote
> thread... =)
>
> Should I drop that vote, fix this, and run a new vote here?
>
> A.
First, fix the problem.
I personally wouldn't stop the vote now - you've got 3 +1s from IPMC
members, and none of us have yet changed our vote, if you get pushback
from other mentors or IPMC members, deal with it as it comes. I
personally don't see this as a blocker, particularly if its already
been fixed and will be remedied in the next release. Just a few more
pieces that need cleanup that were missed.
--David
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
Argh. Of course this pops up right after I start the general@ vote
thread... =)
Should I drop that vote, fix this, and run a new vote here?
A.
On Sun, Jun 16, 2013 at 7:07 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jun 16, 2013 at 9:45 PM, Andrew Bayer <an...@gmail.com>
> wrote:
> > The "Copyright 2013 jclouds" thing is easily fixed - that's just taken
> from
> > the name of the top-level POM. I'll fix that for all future releases.
> >
>
> I don't know where Suresh found them, but I just located the following:
>
> jclouds-karaf-1.6.1-incubating/README.md:Copyright (C) 2009-2011 jclouds,
> Inc.
> jclouds-1.6.1-incubating/README.md:Copyright (C) 2009-2012 jclouds, Inc.
> jclouds-chef-1.6.1-incubating/resources/NOTICE.txt:Copyright 2009-2012
> jclouds, Inc.
> jclouds-chef-1.6.1-incubating/NOTICE:Copyright 2013 jclouds
>
> The NOTICE files are particularly a problem.
>
> --David
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by David Nalley <da...@gnsa.us>.
On Sun, Jun 16, 2013 at 9:45 PM, Andrew Bayer <an...@gmail.com> wrote:
> The "Copyright 2013 jclouds" thing is easily fixed - that's just taken from
> the name of the top-level POM. I'll fix that for all future releases.
>
I don't know where Suresh found them, but I just located the following:
jclouds-karaf-1.6.1-incubating/README.md:Copyright (C) 2009-2011 jclouds, Inc.
jclouds-1.6.1-incubating/README.md:Copyright (C) 2009-2012 jclouds, Inc.
jclouds-chef-1.6.1-incubating/resources/NOTICE.txt:Copyright 2009-2012
jclouds, Inc.
jclouds-chef-1.6.1-incubating/NOTICE:Copyright 2013 jclouds
The NOTICE files are particularly a problem.
--David
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
The "Copyright 2013 jclouds" thing is easily fixed - that's just taken from
the name of the top-level POM. I'll fix that for all future releases.
in re: NOTICE - so this is, at its core, a difference between how we had
been doing it and how the Apache super-parent POM does it. The standard
Apache NOTICE doesn't have dependencies in it; instead, it's got a separate
DEPENDENCIES file - see
https://svn.apache.org/repos/asf/maven/resources/tags/apache-jar-resource-bundle-1.4/src/main/resources/META-INF/DEPENDENCIES.vmand
https://svn.apache.org/repos/asf/maven/resources/tags/apache-jar-resource-bundle-1.4/src/main/resources/META-INF/NOTICE.vm
.
And the staging repos are dropped - I forgot. =)
A.
On Sun, Jun 16, 2013 at 5:46 PM, Suresh Marru <sm...@apache.org> wrote:
> Great progress Andrew with the release artifacts. I am in email catch up
> mode and might have missed some discussion. So I will post some discussions
> first, will hold vote for now pending this discussion. If these issues have
> been discussed previously I will vote. Meanwhile, I will keep looking.
>
> The signatures all look good, maven builds of all sources success, the
> nexus repo is correctly populated (see improvements below), with required
> NOTICE, LICENSE and DISCLAIMER files.
>
> I am personally not sure "Copyright 2013 jclouds" is a blocker or not. The
> instructions clearly say it has to be Apache $Project -
> http://www.apache.org/legal/src-headers.html#notice
>
> I will not gate this and will vote positively, since the following line
> clearly says the software is developed at ASF, but I will rely on other
> mentor/IPMC opinion on this.
>
> The NOTICE.txt file in previous iterations (example:
> https://repository.apache.org/content/repositories/orgapachejclouds-015/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar)
> has significant dependency notices. Why did these notices did not get
> populated into the current NOTICE file (example -
> https://repository.apache.org/content/repositories/orgapachejclouds-016/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar
> )
>
> Here are some non-blocking comments and suggestions for future
> improvements:
>
> * Please instruct the release vote discussion to [VOTE] and [DISCUSS]
> threads. As soon as you post the [VOTE] thread, immediately post a
> [DISCUSS] email and encourage all review and discussions to discuss thread.
> The vote thread is advised to only have votes. Quick reference examples
> [1], [2]
> * Please try to post the release artifacts to official dev distribution
> area [3] instead of your personal space - (Note the *dev*, this location
> is not mirrored, the *release* area [4] will be).
> * Fix the NOTICE file from jclouds to Apache jclouds
> * Include Project metadata in the parent pom - Mailing List, Issue
> Management, Developers. Example if needed [5].
> * As David already pointed out, try and have atleast 3 apache committers
> sign your key.
> * I would drop all the cancelled RC nexus repo's before pushing new RC's.
> Currently you will see 7 staging repos -
> https://repository.apache.org/index.html#stagingRepositories. Except the
> orgapachejclouds-016, please drop others.
>
> Suresh
> [1] - http://airavata.apache.org/development/release-vote.txt
> [2] - http://airavata.apache.org/development/release-discuss.txt
> [3] - https://dist.apache.org/repos/dist/dev/incubator/jclouds/
> [4] - https://dist.apache.org/repos/dist/release/incubator/jclouds/
> [5] - https://svn.apache.org/repos/asf/airavata/trunk/pom.xml
>
> On Jun 12, 2013, at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>
> > Hello,
> >
> > This is the third release candidate for Apache jclouds 1.6.1-incubating,
> > the first jclouds release at Apache.
> >
> > This is a PPMC vote - if this passes, we'll move it onward to an IPMC
> vote.
> >
> > It fixes the following issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
> >
> > *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachejclouds-016
> >
> > The tags to be voted upon:
> > - jclouds -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
> > - jclouds-labs -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
> > - jclouds-chef -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
> > - jclouds-karaf -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
> > - jclouds-cli -
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
> >
> > jclouds KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/incubator/jclouds/KEYS
> >
> > [ ] +1
> > [ ] 0
> > [ ] -1 (explain why)
> >
> > A.
>
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Suresh Marru <sm...@apache.org>.
Great progress Andrew with the release artifacts. I am in email catch up mode and might have missed some discussion. So I will post some discussions first, will hold vote for now pending this discussion. If these issues have been discussed previously I will vote. Meanwhile, I will keep looking.
The signatures all look good, maven builds of all sources success, the nexus repo is correctly populated (see improvements below), with required NOTICE, LICENSE and DISCLAIMER files.
I am personally not sure "Copyright 2013 jclouds" is a blocker or not. The instructions clearly say it has to be Apache $Project - http://www.apache.org/legal/src-headers.html#notice
I will not gate this and will vote positively, since the following line clearly says the software is developed at ASF, but I will rely on other mentor/IPMC opinion on this.
The NOTICE.txt file in previous iterations (example: https://repository.apache.org/content/repositories/orgapachejclouds-015/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar) has significant dependency notices. Why did these notices did not get populated into the current NOTICE file (example - https://repository.apache.org/content/repositories/orgapachejclouds-016/org/apache/jclouds/api/ec2/1.6.1-incubating/ec2-1.6.1-incubating.jar)
Here are some non-blocking comments and suggestions for future improvements:
* Please instruct the release vote discussion to [VOTE] and [DISCUSS] threads. As soon as you post the [VOTE] thread, immediately post a [DISCUSS] email and encourage all review and discussions to discuss thread. The vote thread is advised to only have votes. Quick reference examples [1], [2]
* Please try to post the release artifacts to official dev distribution area [3] instead of your personal space - (Note the *dev*, this location is not mirrored, the *release* area [4] will be).
* Fix the NOTICE file from jclouds to Apache jclouds
* Include Project metadata in the parent pom - Mailing List, Issue Management, Developers. Example if needed [5].
* As David already pointed out, try and have atleast 3 apache committers sign your key.
* I would drop all the cancelled RC nexus repo's before pushing new RC's. Currently you will see 7 staging repos - https://repository.apache.org/index.html#stagingRepositories. Except the orgapachejclouds-016, please drop others.
Suresh
[1] - http://airavata.apache.org/development/release-vote.txt
[2] - http://airavata.apache.org/development/release-discuss.txt
[3] - https://dist.apache.org/repos/dist/dev/incubator/jclouds/
[4] - https://dist.apache.org/repos/dist/release/incubator/jclouds/
[5] - https://svn.apache.org/repos/asf/airavata/trunk/pom.xml
On Jun 12, 2013, at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
> Hello,
>
> This is the third release candidate for Apache jclouds 1.6.1-incubating,
> the first jclouds release at Apache.
>
> This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>
> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachejclouds-016
>
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
>
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
>
> A.
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Andrew Bayer <an...@gmail.com>.
FYI, I'm extending this vote to 7pm PDT on Sunday, to give everyone the
chance to review and vote.
Also, I'm +1, binding, PPMC.
A.
On Thu, Jun 13, 2013 at 1:24 AM, Ignasi <ig...@gmail.com> wrote:
> Hi David,
>
> This was discussed here [1] and addressed here [2]. Those files are
> script fragments that are composed to build complex scripts. All those
> script files in src/test/resources have the corresponding script
> fragment in src/main/resources/functions, and all those fragments have
> the appropriate headers.
>
> However, as said in the thread, we are removing the license headers of
> the fragments at runtime when loading the files, so the final composed
> script has only one header at the top. That means that in runtime,
> single fragments won't have a license header, and that is the reason
> why files in src/test/resources don't have them: to properly assert in
> unit tests that the license "remove" when loading fragments actually
> works and we end up with a composed script with only one header at the
> top.
>
>
> Hope this makes sense,
>
>
> Ignasi
>
> [1] http://markmail.org/message/emu4axdy3qzqxjto
> [2] https://issues.apache.org/jira/browse/JCLOUDS-67
>
> On 13 June 2013 06:51, David Nalley <da...@gnsa.us> wrote:
> > On Wed, Jun 12, 2013 at 9:35 PM, Andrew Bayer <an...@gmail.com>
> wrote:
> >> Hello,
> >>
> >> This is the third release candidate for Apache jclouds 1.6.1-incubating,
> >> the first jclouds release at Apache.
> >>
> >> This is a PPMC vote - if this passes, we'll move it onward to an IPMC
> vote.
> >>
> >> It fixes the following issues:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
> >>
> >> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
> >>
> >> Note that we are voting upon the source (tag), binaries are provided for
> >> convenience.
> >>
> >> Source and binary files:
> >> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
> >>
> >> Maven staging repo:
> >> https://repository.apache.org/content/repositories/orgapachejclouds-016
> >>
> >> The tags to be voted upon:
> >> - jclouds -
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
> >> - jclouds-labs -
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
> >> - jclouds-chef -
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
> >> - jclouds-karaf -
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
> >> - jclouds-cli -
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
> >>
> >> jclouds KEYS file containing PGP keys we use to sign the release:
> >> http://www.apache.org/dist/incubator/jclouds/KEYS
> >>
> >> [ ] +1
> >> [ ] 0
> >> [ ] -1 (explain why)
> >>
> >> A.
> >
> > Overall looking good -
> >
> > Did we talk about the files in scriptbuilder/src/test/resources in
> > jclouds tarball itself?
> >
> > I can't seem to find a record of it. Can someone explain why we don't
> > have license headers on those files.
> >
> > --David
>
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by Ignasi <ig...@gmail.com>.
Hi David,
This was discussed here [1] and addressed here [2]. Those files are
script fragments that are composed to build complex scripts. All those
script files in src/test/resources have the corresponding script
fragment in src/main/resources/functions, and all those fragments have
the appropriate headers.
However, as said in the thread, we are removing the license headers of
the fragments at runtime when loading the files, so the final composed
script has only one header at the top. That means that in runtime,
single fragments won't have a license header, and that is the reason
why files in src/test/resources don't have them: to properly assert in
unit tests that the license "remove" when loading fragments actually
works and we end up with a composed script with only one header at the
top.
Hope this makes sense,
Ignasi
[1] http://markmail.org/message/emu4axdy3qzqxjto
[2] https://issues.apache.org/jira/browse/JCLOUDS-67
On 13 June 2013 06:51, David Nalley <da...@gnsa.us> wrote:
> On Wed, Jun 12, 2013 at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
>> Hello,
>>
>> This is the third release candidate for Apache jclouds 1.6.1-incubating,
>> the first jclouds release at Apache.
>>
>> This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
>>
>> It fixes the following issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>>
>> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>>
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>>
>> Source and binary files:
>> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachejclouds-016
>>
>> The tags to be voted upon:
>> - jclouds -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
>> - jclouds-labs -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
>> - jclouds-chef -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
>> - jclouds-karaf -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
>> - jclouds-cli -
>> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>>
>> jclouds KEYS file containing PGP keys we use to sign the release:
>> http://www.apache.org/dist/incubator/jclouds/KEYS
>>
>> [ ] +1
>> [ ] 0
>> [ ] -1 (explain why)
>>
>> A.
>
> Overall looking good -
>
> Did we talk about the files in scriptbuilder/src/test/resources in
> jclouds tarball itself?
>
> I can't seem to find a record of it. Can someone explain why we don't
> have license headers on those files.
>
> --David
Re: [VOTE] Release Apache jclouds 1.6.1-incubating RC3
Posted by David Nalley <da...@gnsa.us>.
On Wed, Jun 12, 2013 at 9:35 PM, Andrew Bayer <an...@gmail.com> wrote:
> Hello,
>
> This is the third release candidate for Apache jclouds 1.6.1-incubating,
> the first jclouds release at Apache.
>
> This is a PPMC vote - if this passes, we'll move it onward to an IPMC vote.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412&styleName=Html&projectId=12314430
>
> *** Please download, test and vote by Saturday, June 15th, 7pm PDT.
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachejclouds-016
>
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5
>
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
>
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
>
> A.
Overall looking good -
Did we talk about the files in scriptbuilder/src/test/resources in
jclouds tarball itself?
I can't seem to find a record of it. Can someone explain why we don't
have license headers on those files.
--David