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 Phillips <ap...@qrmedia.com> on 2013/08/01 18:46:31 UTC
Code freeze for 1.6.2-incubating tomorrow 09:00 EST
With so much last minute activity going on, it seems to make more
sense to move the code freeze out a little rather than rushing things.
So code freeze for the 1.6.x branch will now be:
Tomorrow, Friday Aug 02 at 09:00 EST
Then the 1.6.2-incubating show will hit the road!
ap
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Bayer <an...@gmail.com>.
Update the wiki - the move to include labs-openstack happened like two days
ago. =)
A.
On Fri, Aug 2, 2013 at 7:10 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
> What about jclouds-labs-openstack?
>>
>> That needs to be part of the release process too.
>>
>
> Erm...indeedy! Well, spotted, thanks! Please consider the following repos
> also frozen, for now:
>
> * incubating-jclouds-labs-**openstack.git
>
> frozen at https://git-wip-us.apache.org/**repos/asf?p=incubator-jclouds-**
> labs-openstack.git;a=commit;h=**dd2b5a68fd184efbdcb9ccedbee37e**b922efdc6a<https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-openstack.git;a=commit;h=dd2b5a68fd184efbdcb9ccedbee37eb922efdc6a>
>
> incubating-jclouds-labs-aws and incubating-jclouds-labs-google don't
> appear to have 1.6.x branches, so ignoring those.
>
> @abayer: was labs-openstack omitted from the release instructions
> intentionally, or can I simply update the Wiki page?
>
> ap
>
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Phillips <ap...@qrmedia.com>.
> What about jclouds-labs-openstack?
>
> That needs to be part of the release process too.
Erm...indeedy! Well, spotted, thanks! Please consider the following
repos also frozen, for now:
* incubating-jclouds-labs-openstack.git
frozen at
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-openstack.git;a=commit;h=dd2b5a68fd184efbdcb9ccedbee37eb922efdc6a
incubating-jclouds-labs-aws and incubating-jclouds-labs-google don't
appear to have 1.6.x branches, so ignoring those.
@abayer: was labs-openstack omitted from the release instructions
intentionally, or can I simply update the Wiki page?
ap
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Everett Toews <ev...@RACKSPACE.COM>.
What about jclouds-labs-openstack?
That needs to be part of the release process too.
Thanks,
Everett
On Aug 2, 2013, at 8:38 AM, Andrew Phillips wrote:
> As per the discussion, [lease consider the following repos as "frozen":
>
> * incubating-jclouds.git
>
> frozen at https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=8688d8e0c3803295c52e912e5a6d543c841fbd55
>
> * incubating-jclouds-labs.git
>
> frozen at https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=commit;h=3300d3acf870677accbb65d07298c2e33037b943
>
> * incubating-jclouds-chef.git
>
> frozen at https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=commit;h=44fba95ba5df14c392f5277b36716b66f9a5434e
>
> * incubating-jclouds-karaf.git
>
> frozen at https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=shortlog;h=refs/heads/1.6.x
>
> * incubating-jclouds-cli.git
>
> frozen at https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=commit;h=a08af620e282628528bdc0f34c1ecdb36159623f
>
> We'll get started on the release procedure for 1.6.2-incubating now. Since we're not voting yet, we can still include fixed for any urgent regressions we uncover. I propose that we don't add any new features to 1.6.2-incubating any more, though.
>
> Here goes!
>
> ap
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Phillips <ap...@qrmedia.com>.
As per the discussion, [lease consider the following repos as "frozen":
* incubating-jclouds.git
frozen at
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=8688d8e0c3803295c52e912e5a6d543c841fbd55
* incubating-jclouds-labs.git
frozen at
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=commit;h=3300d3acf870677accbb65d07298c2e33037b943
* incubating-jclouds-chef.git
frozen at
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=commit;h=44fba95ba5df14c392f5277b36716b66f9a5434e
* incubating-jclouds-karaf.git
frozen at
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=shortlog;h=refs/heads/1.6.x
* incubating-jclouds-cli.git
frozen at
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=commit;h=a08af620e282628528bdc0f34c1ecdb36159623f
We'll get started on the release procedure for 1.6.2-incubating now.
Since we're not voting yet, we can still include fixed for any urgent
regressions we uncover. I propose that we don't add any new features
to 1.6.2-incubating any more, though.
Here goes!
ap
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Bayer <an...@gmail.com>.
I've been running the CloudStack live tests fairly often, both for testing
the changes I've made lately and for my work on running the live tests
against the ACS simulator, so I'm pretty confident of it.
A.
On Thu, Aug 1, 2013 at 11:02 AM, Andrew Gaul <ga...@apache.org> wrote:
> I will run all integration tests against the major blobstore providers
> tonight:
>
> atmos
> aws-s3
> azure
> cloudfiles
> hpcloud-objectstorage
>
> On Thu, Aug 01, 2013 at 10:58:42AM -0700, Matt Stephenson wrote:
> > I don't have bandwidth, but perhaps someone should run the livetests this
> > afternoon just to verify nothing's been broken in the last minute
> changes,
> > before we're in go-mode tomorrow.
> >
> >
> >
> > On Thu, Aug 1, 2013 at 9:46 AM, Andrew Phillips <aphillips@qrmedia.com
> >wrote:
> >
> > > With so much last minute activity going on, it seems to make more
> sense to
> > > move the code freeze out a little rather than rushing things.
> > >
> > > So code freeze for the 1.6.x branch will now be:
> > >
> > > Tomorrow, Friday Aug 02 at 09:00 EST
> > >
> > > Then the 1.6.2-incubating show will hit the road!
> > >
> > > ap
> > >
>
> --
> Andrew Gaul
> http://gaul.org/
>
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Phillips <ap...@qrmedia.com>.
> I will run all integration tests against the major blobstore providers
> tonight:
>
> atmos
> aws-s3
> azure
> cloudfiles
> hpcloud-objectstorage
Great, thanks! Anyone available to do some of this for compute?
ap
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Gaul <ga...@apache.org>.
I ran all the blobstore integration tests and attached the results. I
already opened issues for the aws-s3 and cloudfiles failures:
https://issues.apache.org/jira/browse/JCLOUDS-96
https://issues.apache.org/jira/browse/JCLOUDS-179
hpcloud-objectstorage shares one failure with cloudfiles and has two
other bucket naming failures. azure and atmos both fail in
testBigFileGets which I have not yet investigated. Atmos has some
further directory failures. I do not believe that these integration
test failures should block 1.6.2 and I will try to address them in
1.6.3.
On Thu, Aug 01, 2013 at 11:02:09AM -0700, Andrew Gaul wrote:
> I will run all integration tests against the major blobstore providers
> tonight:
>
> atmos
> aws-s3
> azure
> cloudfiles
> hpcloud-objectstorage
>
> On Thu, Aug 01, 2013 at 10:58:42AM -0700, Matt Stephenson wrote:
> > I don't have bandwidth, but perhaps someone should run the livetests this
> > afternoon just to verify nothing's been broken in the last minute changes,
> > before we're in go-mode tomorrow.
> >
> >
> >
> > On Thu, Aug 1, 2013 at 9:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
> >
> > > With so much last minute activity going on, it seems to make more sense to
> > > move the code freeze out a little rather than rushing things.
> > >
> > > So code freeze for the 1.6.x branch will now be:
> > >
> > > Tomorrow, Friday Aug 02 at 09:00 EST
> > >
> > > Then the 1.6.2-incubating show will hit the road!
> > >
> > > ap
> > >
--
Andrew Gaul
http://gaul.org/
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Andrew Gaul <ga...@apache.org>.
I will run all integration tests against the major blobstore providers
tonight:
atmos
aws-s3
azure
cloudfiles
hpcloud-objectstorage
On Thu, Aug 01, 2013 at 10:58:42AM -0700, Matt Stephenson wrote:
> I don't have bandwidth, but perhaps someone should run the livetests this
> afternoon just to verify nothing's been broken in the last minute changes,
> before we're in go-mode tomorrow.
>
>
>
> On Thu, Aug 1, 2013 at 9:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>
> > With so much last minute activity going on, it seems to make more sense to
> > move the code freeze out a little rather than rushing things.
> >
> > So code freeze for the 1.6.x branch will now be:
> >
> > Tomorrow, Friday Aug 02 at 09:00 EST
> >
> > Then the 1.6.2-incubating show will hit the road!
> >
> > ap
> >
--
Andrew Gaul
http://gaul.org/
Re: Code freeze for 1.6.2-incubating tomorrow 09:00 EST
Posted by Matt Stephenson <ma...@mattstep.net>.
I don't have bandwidth, but perhaps someone should run the livetests this
afternoon just to verify nothing's been broken in the last minute changes,
before we're in go-mode tomorrow.
On Thu, Aug 1, 2013 at 9:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
> With so much last minute activity going on, it seems to make more sense to
> move the code freeze out a little rather than rushing things.
>
> So code freeze for the 1.6.x branch will now be:
>
> Tomorrow, Friday Aug 02 at 09:00 EST
>
> Then the 1.6.2-incubating show will hit the road!
>
> ap
>