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/12/16 16:37:06 UTC

Ready to go for 1.7.0?

So, are we ready for cutting the release today? =)

A.

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

Sure thing!


On Mon, Dec 16, 2013 at 9:11 AM, Everett Toews
<ev...@rackspace.com>wrote:

> Pretty close. When did you want to get started?
>
> How about 1:00 pm PST?
>
> Everett
>
>
> On Dec 16, 2013, at 9:37 AM, Andrew Bayer wrote:
>
> > So, are we ready for cutting the release today? =)
> >
> > A.
>
>

Re: Ready to go for 1.7.0?

Posted by Andrew Gaul <ga...@apache.org>.

I have a few straggling patches on GitHub which I will commit by 1 PM.

On Mon, Dec 16, 2013 at 05:11:28PM +0000, Everett Toews wrote:
> Pretty close. When did you want to get started?
> 
> How about 1:00 pm PST?
> 
> Everett
> 
> 
> On Dec 16, 2013, at 9:37 AM, Andrew Bayer wrote:
> 
> > So, are we ready for cutting the release today? =)
> > 
> > A.

-- 
Andrew Gaul
http://gaul.org/

Re: Ready to go for 1.7.0?

Posted by Everett Toews <ev...@RACKSPACE.COM>.

Pretty close. When did you want to get started?

How about 1:00 pm PST?

Everett


On Dec 16, 2013, at 9:37 AM, Andrew Bayer wrote:

> So, are we ready for cutting the release today? =)
> 
> A.

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

1.7.x branch cut everywhere but jclouds-labs-openstack - waiting on
Everett's changes there.

A.


On Tue, Dec 17, 2013 at 10:07 AM, Andrew Bayer <an...@gmail.com>wrote:

> Ah, ok. Will do.
>
> A.
>
>
> On Tue, Dec 17, 2013 at 10:04 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>
>> I'll be replacing the tag - I'd assumed we'd do this off master and then
>>> cut 1.7.x branches afterwards, but I'm open to either way.
>>>
>>
>> The first 1.6.0 release commits were also on the 1.6.x branch and not on
>> master [1, 2], so unless we see a good reason to change that pattern I'd
>> say we create 1.7.x first and have the release commits (and any prep
>> commits required) be the first ones on the branch?
>>
>> Good luck, and ping if we can help in any way!
>>
>> ap
>>
>> [1] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=
>> 51cddcb841bf97f6058d71fe06c574c9240fa219
>> [2] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=shortlog;pg=2
>>
>
>

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

Ah, ok. Will do.

A.


On Tue, Dec 17, 2013 at 10:04 AM, Andrew Phillips <ap...@qrmedia.com>wrote:

> I'll be replacing the tag - I'd assumed we'd do this off master and then
>> cut 1.7.x branches afterwards, but I'm open to either way.
>>
>
> The first 1.6.0 release commits were also on the 1.6.x branch and not on
> master [1, 2], so unless we see a good reason to change that pattern I'd
> say we create 1.7.x first and have the release commits (and any prep
> commits required) be the first ones on the branch?
>
> Good luck, and ping if we can help in any way!
>
> ap
>
> [1] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=
> 51cddcb841bf97f6058d71fe06c574c9240fa219
> [2] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=shortlog;pg=2
>

Re: Ready to go for 1.7.0?

Posted by Andrew Phillips <ap...@qrmedia.com>.

> I'll be replacing the tag - I'd assumed we'd do this off master and then
> cut 1.7.x branches afterwards, but I'm open to either way.

The first 1.6.0 release commits were also on the 1.6.x branch and not  
on master [1, 2], so unless we see a good reason to change that  
pattern I'd say we create 1.7.x first and have the release commits  
(and any prep commits required) be the first ones on the branch?

Good luck, and ping if we can help in any way!

ap

[1]  
https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=51cddcb841bf97f6058d71fe06c574c9240fa219
[2] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=shortlog;pg=2

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

Chef looks good, starting the train now.

A.


On Tue, Dec 17, 2013 at 9:48 AM, Andrew Bayer <an...@gmail.com>wrote:

> I'll be replacing the tag - I'd assumed we'd do this off master and then
> cut 1.7.x branches afterwards, but I'm open to either way.
>
> If I'm unable to cut the release today, then yeah, wouldn't hurt if you
> could do it tomorrow, but I think (think!) I'll be able to get it done
> today.
>
> A.
>
>
> On Tue, Dec 17, 2013 at 9:40 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>
>> Ok, waiting to see if chef is actually fixed - if it is, I'll recut the
>>> release today. If not, I'll do it either tomorrow or Thursday. I'm ill
>>> today (blech) and traveling tomorrow, so scheduling is a bit whacky. =)
>>>
>>
>> If you need any help with the release, let me know - I probably could
>> make time to cut this one, if necessary.
>>
>> I notice there's a stray (?) tag already in ASF Git? [1] And are we going
>> to cut this from a new 1.7.x branch?
>>
>> Get better soon!
>>
>> ap
>>
>> [1] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=
>> 2ad79f0211ddf49d650c0161bc6b974e6b398d3b
>>
>
>

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

I'll be replacing the tag - I'd assumed we'd do this off master and then
cut 1.7.x branches afterwards, but I'm open to either way.

If I'm unable to cut the release today, then yeah, wouldn't hurt if you
could do it tomorrow, but I think (think!) I'll be able to get it done
today.

A.

On Tue, Dec 17, 2013 at 9:40 AM, Andrew Phillips <ap...@qrmedia.com>wrote:

> Ok, waiting to see if chef is actually fixed - if it is, I'll recut the
>> release today. If not, I'll do it either tomorrow or Thursday. I'm ill
>> today (blech) and traveling tomorrow, so scheduling is a bit whacky. =)
>>
>
> If you need any help with the release, let me know - I probably could make
> time to cut this one, if necessary.
>
> I notice there's a stray (?) tag already in ASF Git? [1] And are we going
> to cut this from a new 1.7.x branch?
>
> Get better soon!
>
> ap
>
> [1] https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=
> 2ad79f0211ddf49d650c0161bc6b974e6b398d3b
>

Re: Ready to go for 1.7.0?

Posted by Andrew Phillips <ap...@qrmedia.com>.

> Ok, waiting to see if chef is actually fixed - if it is, I'll recut the
> release today. If not, I'll do it either tomorrow or Thursday. I'm ill
> today (blech) and traveling tomorrow, so scheduling is a bit whacky. =)

If you need any help with the release, let me know - I probably could  
make time to cut this one, if necessary.

I notice there's a stray (?) tag already in ASF Git? [1] And are we  
going to cut this from a new 1.7.x branch?

Get better soon!

ap

[1]  
https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=2ad79f0211ddf49d650c0161bc6b974e6b398d3b

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

Ok, waiting to see if chef is actually fixed - if it is, I'll recut the
release today. If not, I'll do it either tomorrow or Thursday. I'm ill
today (blech) and traveling tomorrow, so scheduling is a bit whacky. =)

A.


On Mon, Dec 16, 2013 at 5:28 PM, Andrew Bayer <an...@gmail.com>wrote:

> Working on cutting the release now - FYI, there are a ton of incredibly
> painful points I'm hitting in terms of versioning in jclouds-labs et al,
> which are requiring me to update things by hand. I'm not gonna actually
> update the wiki on that until I've given up trying to find a better way to
> automate it/prevent it from happening in the first place, but if I don't
> succeed in that, the wiki will be updated accordingly.
>
> A.
>
>
> On Mon, Dec 16, 2013 at 3:11 PM, Andrew Bayer <an...@gmail.com>wrote:
>
>> 'K, I'll cut it in the next hour.
>>
>> A.
>>
>>
>>
>> On Dec 16, 2013, at 3:05 PM, Andrew Gaul <ga...@apache.org> wrote:
>>
>> > Ready to go!
>> >
>> > On Mon, Dec 16, 2013 at 12:59:27PM -0800, Andrew Bayer wrote:
>> >> And merged.
>> >>
>> >> Gaul, Everett - could you reply here when you're ready to go?
>> >>
>> >> A.
>> >>
>> >>
>> >> On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <andrew.bayer@gmail.com
>> >wrote:
>> >>
>> >>> I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
>> >>>
>> >>> A.
>> >>>
>> >>>
>> >>> On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <
>> aphillips@qrmedia.com>wrote:
>> >>>
>> >>>> So, are we ready for cutting the release today? =)
>> >>>>>
>> >>>>
>> >>>> Quick sweep of the PRs? Looks like at least the following might be
>> >>>> candidates for 1.7.0?
>> >>>>
>> >>>> https://github.com/jclouds/jclouds/pull/44
>> >>>> https://github.com/jclouds/jclouds/pull/38
>> >>>> https://github.com/jclouds/jclouds/pull/223
>> >>>> https://github.com/jclouds/jclouds/pull/228
>> >>>> https://github.com/jclouds/jclouds/pull/231
>> >>>>
>> >>>> ap
>> >>>>
>> >>>
>> >>>
>> >
>> > --
>> > Andrew Gaul
>> > http://gaul.org/
>>
>
>

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

Working on cutting the release now - FYI, there are a ton of incredibly
painful points I'm hitting in terms of versioning in jclouds-labs et al,
which are requiring me to update things by hand. I'm not gonna actually
update the wiki on that until I've given up trying to find a better way to
automate it/prevent it from happening in the first place, but if I don't
succeed in that, the wiki will be updated accordingly.

A.

On Mon, Dec 16, 2013 at 3:11 PM, Andrew Bayer <an...@gmail.com>wrote:

> 'K, I'll cut it in the next hour.
>
> A.
>
>
>
> On Dec 16, 2013, at 3:05 PM, Andrew Gaul <ga...@apache.org> wrote:
>
> > Ready to go!
> >
> > On Mon, Dec 16, 2013 at 12:59:27PM -0800, Andrew Bayer wrote:
> >> And merged.
> >>
> >> Gaul, Everett - could you reply here when you're ready to go?
> >>
> >> A.
> >>
> >>
> >> On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <andrew.bayer@gmail.com
> >wrote:
> >>
> >>> I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
> >>>
> >>> A.
> >>>
> >>>
> >>> On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <
> aphillips@qrmedia.com>wrote:
> >>>
> >>>> So, are we ready for cutting the release today? =)
> >>>>>
> >>>>
> >>>> Quick sweep of the PRs? Looks like at least the following might be
> >>>> candidates for 1.7.0?
> >>>>
> >>>> https://github.com/jclouds/jclouds/pull/44
> >>>> https://github.com/jclouds/jclouds/pull/38
> >>>> https://github.com/jclouds/jclouds/pull/223
> >>>> https://github.com/jclouds/jclouds/pull/228
> >>>> https://github.com/jclouds/jclouds/pull/231
> >>>>
> >>>> ap
> >>>>
> >>>
> >>>
> >
> > --
> > Andrew Gaul
> > http://gaul.org/
>

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

'K, I'll cut it in the next hour.

A.



On Dec 16, 2013, at 3:05 PM, Andrew Gaul <ga...@apache.org> wrote:

> Ready to go!
> 
> On Mon, Dec 16, 2013 at 12:59:27PM -0800, Andrew Bayer wrote:
>> And merged.
>> 
>> Gaul, Everett - could you reply here when you're ready to go?
>> 
>> A.
>> 
>> 
>> On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <an...@gmail.com>wrote:
>> 
>>> I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
>>> 
>>> A.
>>> 
>>> 
>>> On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>>> 
>>>> So, are we ready for cutting the release today? =)
>>>>> 
>>>> 
>>>> Quick sweep of the PRs? Looks like at least the following might be
>>>> candidates for 1.7.0?
>>>> 
>>>> https://github.com/jclouds/jclouds/pull/44
>>>> https://github.com/jclouds/jclouds/pull/38
>>>> https://github.com/jclouds/jclouds/pull/223
>>>> https://github.com/jclouds/jclouds/pull/228
>>>> https://github.com/jclouds/jclouds/pull/231
>>>> 
>>>> ap
>>>> 
>>> 
>>> 
> 
> -- 
> Andrew Gaul
> http://gaul.org/

Re: Ready to go for 1.7.0?

Posted by Andrew Gaul <ga...@apache.org>.

Ready to go!

On Mon, Dec 16, 2013 at 12:59:27PM -0800, Andrew Bayer wrote:
> And merged.
> 
> Gaul, Everett - could you reply here when you're ready to go?
> 
> A.
> 
> 
> On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <an...@gmail.com>wrote:
> 
> > I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
> >
> > A.
> >
> >
> > On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
> >
> >>  So, are we ready for cutting the release today? =)
> >>>
> >>
> >> Quick sweep of the PRs? Looks like at least the following might be
> >> candidates for 1.7.0?
> >>
> >> https://github.com/jclouds/jclouds/pull/44
> >> https://github.com/jclouds/jclouds/pull/38
> >> https://github.com/jclouds/jclouds/pull/223
> >> https://github.com/jclouds/jclouds/pull/228
> >> https://github.com/jclouds/jclouds/pull/231
> >>
> >> ap
> >>
> >
> >

-- 
Andrew Gaul
http://gaul.org/

Re: Ready to go for 1.7.0?

Posted by Everett Toews <ev...@RACKSPACE.COM>.

Okay. We're skipping that one.

We're ready to go.

Thanks!
Everett


On Dec 16, 2013, at 3:08 PM, Everett Toews wrote:

> Waiting on builds for 
> 
> https://github.com/jclouds/jclouds/pull/237
> 
> will merge shortly.
> 
> Thanks,
> Everett
> 
> 
> On Dec 16, 2013, at 2:59 PM, Andrew Bayer wrote:
> 
>> And merged.
>> 
>> Gaul, Everett - could you reply here when you're ready to go?
>> 
>> A.
>> 
>> 
>> On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <an...@gmail.com>wrote:
>> 
>>> I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
>>> 
>>> A.
>>> 
>>> 
>>> On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>>> 
>>>> So, are we ready for cutting the release today? =)
>>>>> 
>>>> 
>>>> Quick sweep of the PRs? Looks like at least the following might be
>>>> candidates for 1.7.0?
>>>> 
>>>> https://github.com/jclouds/jclouds/pull/44
>>>> https://github.com/jclouds/jclouds/pull/38
>>>> https://github.com/jclouds/jclouds/pull/223
>>>> https://github.com/jclouds/jclouds/pull/228
>>>> https://github.com/jclouds/jclouds/pull/231
>>>> 
>>>> ap
>>>> 
>>> 
>>> 
>

Re: Ready to go for 1.7.0?

Posted by Everett Toews <ev...@RACKSPACE.COM>.

Waiting on builds for 

https://github.com/jclouds/jclouds/pull/237

will merge shortly.

Thanks,
Everett


On Dec 16, 2013, at 2:59 PM, Andrew Bayer wrote:

> And merged.
> 
> Gaul, Everett - could you reply here when you're ready to go?
> 
> A.
> 
> 
> On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <an...@gmail.com>wrote:
> 
>> I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
>> 
>> A.
>> 
>> 
>> On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>> 
>>> So, are we ready for cutting the release today? =)
>>>> 
>>> 
>>> Quick sweep of the PRs? Looks like at least the following might be
>>> candidates for 1.7.0?
>>> 
>>> https://github.com/jclouds/jclouds/pull/44
>>> https://github.com/jclouds/jclouds/pull/38
>>> https://github.com/jclouds/jclouds/pull/223
>>> https://github.com/jclouds/jclouds/pull/228
>>> https://github.com/jclouds/jclouds/pull/231
>>> 
>>> ap
>>> 
>> 
>>

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

And merged.

Gaul, Everett - could you reply here when you're ready to go?

A.


On Mon, Dec 16, 2013 at 12:45 PM, Andrew Bayer <an...@gmail.com>wrote:

> I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.
>
> A.
>
>
> On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
>
>>  So, are we ready for cutting the release today? =)
>>>
>>
>> Quick sweep of the PRs? Looks like at least the following might be
>> candidates for 1.7.0?
>>
>> https://github.com/jclouds/jclouds/pull/44
>> https://github.com/jclouds/jclouds/pull/38
>> https://github.com/jclouds/jclouds/pull/223
>> https://github.com/jclouds/jclouds/pull/228
>> https://github.com/jclouds/jclouds/pull/231
>>
>> ap
>>
>
>

Re: Ready to go for 1.7.0?

Posted by Andrew Bayer <an...@gmail.com>.

I'll merge https://github.com/jclouds/jclouds/pull/228 shortly.

A.


On Mon, Dec 16, 2013 at 8:46 AM, Andrew Phillips <ap...@qrmedia.com>wrote:

>  So, are we ready for cutting the release today? =)
>>
>
> Quick sweep of the PRs? Looks like at least the following might be
> candidates for 1.7.0?
>
> https://github.com/jclouds/jclouds/pull/44
> https://github.com/jclouds/jclouds/pull/38
> https://github.com/jclouds/jclouds/pull/223
> https://github.com/jclouds/jclouds/pull/228
> https://github.com/jclouds/jclouds/pull/231
>
> ap
>

Re: Ready to go for 1.7.0?

Posted by Andrew Phillips <ap...@qrmedia.com>.

> So, are we ready for cutting the release today? =)

Quick sweep of the PRs? Looks like at least the following might be  
candidates for 1.7.0?

https://github.com/jclouds/jclouds/pull/44
https://github.com/jclouds/jclouds/pull/38
https://github.com/jclouds/jclouds/pull/223
https://github.com/jclouds/jclouds/pull/228
https://github.com/jclouds/jclouds/pull/231

ap