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 Gaul <ga...@apache.org> on 2013/11/27 00:52:35 UTC
[DISCUSS] Release Apache jclouds-1.6.3-rc2
This thread is for discussion of the second release candidate for Apache
jclouds-1.6.3. Please use this thread for discussion of issues uncovered
in the RC, questions you may have about the RC, etc. Thank you.
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Everett Toews <ev...@RACKSPACE.COM>.
I realize this is after-the-fact but I ran the Rackspace SmokeTest [1] against 1.6.3-rc2 and everything ran perfectly. Sorry I didn't have a chance to do a full verification over the past week.
Cheers,
Everett
[1] https://github.com/jclouds/jclouds-examples/blob/master/rackspace/src/main/java/org/jclouds/examples/rackspace/SmokeTest.java
On Nov 29, 2013, at 12:28 AM, Andrew Gaul wrote:
> Sorry, without a show-stopper or regression issue, we will continue with
> 1.6.3 as-is. This release stretched beyond jclouds usual six-week
> cadence due to graduation from the incubator and we can address further
> issues in 1.6.4 or 1.7.0. I appreciate that a commit missing a given
> release inconveniences some users but believe that this argues for more
> *releases* not more release *candidates*.
>
> On Thu, Nov 28, 2013 at 06:45:39PM +0000, Alex Heneveld wrote:
>>
>> Thanks Andrew P.
>>
>> Sorry for posting to the wrong thread. There is something funny in how
>> [THREAD] prefixes are getting ignored (just mentioning in case anyone else
>> has that) somewhere between Thunderbird and Google Mail.
>>
>> I've also backported the oauth live tests fix at [4] fixing live test
>> failures with 1.6.3-rc2.
>>
>> Between this and the copyright normalisation maybe an rc3 argument can be
>> made after all! :)
>>
>> Best
>> Alex
>>
>>
>> [4] https://github.com/jclouds/jclouds-labs/pull/42
>>
>>
>> On 28/11/2013 15:30, Andrew Phillips wrote:
>>> Moving Alex Heneveld's question to the [DISCUSS] thread...
>>>
>>> "Hi folks-
>>>
>>> The GCE identity parse fix ([2] and [3]) did not get backported. This will
>>> cause problems for many users of GCE.
>>>
>>> I've created a PR for this backport now at [1].
>>>
>>> Would it be possible to cut a new RC for 1.6.3 including this? I know
>>> it's work but GCE is the fastest cloud that I've come across so it would
>>> be nice to have! (Good news is that testing with other clouds all is
>>> good, including the recent changes to Softlayer.)
>>>
>>> Best
>>> Alex
>>>
>>>
>>> [1] https://github.com/jclouds/jclouds-labs/pull/42
>>> [2] https://issues.apache.org/jira/browse/JCLOUDS-362
>>> [3] https://issues.apache.org/jira/browse/JCLOUDS-289"
>
> --
> Andrew Gaul
> http://gaul.org/
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Andrew Gaul <ga...@apache.org>.
Sorry, without a show-stopper or regression issue, we will continue with
1.6.3 as-is. This release stretched beyond jclouds usual six-week
cadence due to graduation from the incubator and we can address further
issues in 1.6.4 or 1.7.0. I appreciate that a commit missing a given
release inconveniences some users but believe that this argues for more
*releases* not more release *candidates*.
On Thu, Nov 28, 2013 at 06:45:39PM +0000, Alex Heneveld wrote:
>
> Thanks Andrew P.
>
> Sorry for posting to the wrong thread. There is something funny in how
> [THREAD] prefixes are getting ignored (just mentioning in case anyone else
> has that) somewhere between Thunderbird and Google Mail.
>
> I've also backported the oauth live tests fix at [4] fixing live test
> failures with 1.6.3-rc2.
>
> Between this and the copyright normalisation maybe an rc3 argument can be
> made after all! :)
>
> Best
> Alex
>
>
> [4] https://github.com/jclouds/jclouds-labs/pull/42
>
>
> On 28/11/2013 15:30, Andrew Phillips wrote:
> >Moving Alex Heneveld's question to the [DISCUSS] thread...
> >
> >"Hi folks-
> >
> >The GCE identity parse fix ([2] and [3]) did not get backported. This will
> >cause problems for many users of GCE.
> >
> >I've created a PR for this backport now at [1].
> >
> >Would it be possible to cut a new RC for 1.6.3 including this? I know
> >it's work but GCE is the fastest cloud that I've come across so it would
> >be nice to have! (Good news is that testing with other clouds all is
> >good, including the recent changes to Softlayer.)
> >
> >Best
> >Alex
> >
> >
> >[1] https://github.com/jclouds/jclouds-labs/pull/42
> >[2] https://issues.apache.org/jira/browse/JCLOUDS-362
> >[3] https://issues.apache.org/jira/browse/JCLOUDS-289"
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
Thanks Andrew P.
Sorry for posting to the wrong thread. There is something funny in how
[THREAD] prefixes are getting ignored (just mentioning in case anyone
else has that) somewhere between Thunderbird and Google Mail.
I've also backported the oauth live tests fix at [4] fixing live test
failures with 1.6.3-rc2.
Between this and the copyright normalisation maybe an rc3 argument can
be made after all! :)
Best
Alex
[4] https://github.com/jclouds/jclouds-labs/pull/42
On 28/11/2013 15:30, Andrew Phillips wrote:
> Moving Alex Heneveld's question to the [DISCUSS] thread...
>
> "Hi folks-
>
> The GCE identity parse fix ([2] and [3]) did not get backported. This
> will cause problems for many users of GCE.
>
> I've created a PR for this backport now at [1].
>
> Would it be possible to cut a new RC for 1.6.3 including this? I know
> it's work but GCE is the fastest cloud that I've come across so it
> would be nice to have! (Good news is that testing with other clouds
> all is good, including the recent changes to Softlayer.)
>
> Best
> Alex
>
>
> [1] https://github.com/jclouds/jclouds-labs/pull/42
> [2] https://issues.apache.org/jira/browse/JCLOUDS-362
> [3] https://issues.apache.org/jira/browse/JCLOUDS-289"
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Andrew Phillips <ap...@qrmedia.com>.
Added the following snippet to the Windows version of the verification
script [1]"
set ARCHIVES_LOGFILE=archives.txt
for /D %%i in (jclouds*) do (
echo Seaching in %%i >> "%ARCHIVES_LOGFILE%"
for %%j in (.jar,.bin,.zip,.tar.gz) do (
echo Seaching for %%j... >> "%ARCHIVES_LOGFILE%"
dir /S /B %%i\*%%j >> "%ARCHIVES_LOGFILE%" 2>&1
)
)
Does this make sense? Should we add something similar to the Unix version?
ap
[1] http://people.apache.org/~andrewp/verify-jclouds.cmd
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Andrew Phillips <ap...@qrmedia.com>.
Came across some variations on the NOTICE files:
jclouds:
Apache jclouds
Copyright 2009-2013 The Apache Software Foundation
jclouds-chef:
Apache jclouds Chef
Copyright 2013 The Apache Software Foundation
jclouds-cli:
Apache jclouds :: cli
Copyright 2013 The Apache Software Foundation
jclouds-karaf:
Apache jclouds :: Karaf
Copyright 2013 The Apache Software Foundation
jclouds-labs:
Apache jclouds labs
Copyright 2009-2013 The Apache Software Foundation
jclouds-labs-openstack:
Apache jclouds labs openstack
Copyright 2009-2013 The Apache Software Foundation
I guess the different copyright dates are the main thing. Certainly
something to align for next time, but what about this release?
ap
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Would it be possible to cut a new RC for 1.6.3 including this?
I'm -0 on this one. Would prefer to get 1.6.3 out of the door, focus
on a timely 1.7.0 and then spin a quick(er) 1.6.4 early next year. But
I think ultimately this is a decision for the release manager.
Over to you, Gaul ;-)
ap
Re: [DISCUSS] Release Apache jclouds-1.6.3-rc2
Posted by Andrew Phillips <ap...@qrmedia.com>.
Moving Alex Heneveld's question to the [DISCUSS] thread...
"Hi folks-
The GCE identity parse fix ([2] and [3]) did not get backported. This
will cause problems for many users of GCE.
I've created a PR for this backport now at [1].
Would it be possible to cut a new RC for 1.6.3 including this? I know
it's work but GCE is the fastest cloud that I've come across so it
would be nice to have! (Good news is that testing with other clouds
all is good, including the recent changes to Softlayer.)
Best
Alex
[1] https://github.com/jclouds/jclouds-labs/pull/42
[2] https://issues.apache.org/jira/browse/JCLOUDS-362
[3] https://issues.apache.org/jira/browse/JCLOUDS-289"