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 2014/02/05 19:58:37 UTC
Fwd: Re: Bug Fix Release Date
Forwarding this to the dev@ list...
TL;DR: Fine by me if we're OK to release with a workaround and without
a fixed Guava version.
> This bug is really hurting our users. We need to stop the bleeding.
> Were constantly asking users to use a snapshot release but what we
> really need to do is give them a proper release with the workaround.
>
> I think we should do a 1.7.1 release as soon as possible.
Can do, as long as we're OK with the fact that the release will
contain the workaround we had to apply. 1.7.x is still on Guava 15 and
as far as I can see the Guava team has not released a patch for that
(although there are users in the issue asking for that).
Bumping 1.7.x to a different Guava version was "out of bounds" last I
recall, as users have complained about the previously too.
ap
Re: Bug Fix Release Date
Posted by Ignasi Barrera <ig...@gmail.com>.
I'll start the release process right now. Consider the 1.7.x branch frozen!
On 5 February 2014 23:40, Ignasi Barrera <ig...@gmail.com> wrote:
> Just merged the DigitalOcean provider. I'd consider the branch frozen
> tomorrow at 9am CET. If you have some (very) urgent change to commit,
> that's the window you have :)
>
> On 5 February 2014 22:13, Andrew Phillips <ap...@qrmedia.com> wrote:
>>> I'll cut the release tomorrow then and will include the DigitalOcean
>>> provider.
>>>
>>> I plan to start the release tomorrow at 9:00 AM (CET), which is in 12
>>> hours or so and if I get in trouble I'll wait for you :) Does this
>>> work?
>>
>>
>> Works for me too. Thanks, Ignasi! I guess that means that 1.7.x is
>> considered "frozen" until further notice for everyone except Ignasi..?
>>
>> ap
Re: Bug Fix Release Date
Posted by Ignasi Barrera <ig...@gmail.com>.
Just merged the DigitalOcean provider. I'd consider the branch frozen
tomorrow at 9am CET. If you have some (very) urgent change to commit,
that's the window you have :)
On 5 February 2014 22:13, Andrew Phillips <ap...@qrmedia.com> wrote:
>> I'll cut the release tomorrow then and will include the DigitalOcean
>> provider.
>>
>> I plan to start the release tomorrow at 9:00 AM (CET), which is in 12
>> hours or so and if I get in trouble I'll wait for you :) Does this
>> work?
>
>
> Works for me too. Thanks, Ignasi! I guess that means that 1.7.x is
> considered "frozen" until further notice for everyone except Ignasi..?
>
> ap
Re: Bug Fix Release Date
Posted by Andrew Phillips <ap...@qrmedia.com>.
> I'll cut the release tomorrow then and will include the DigitalOcean
> provider.
>
> I plan to start the release tomorrow at 9:00 AM (CET), which is in 12
> hours or so and if I get in trouble I'll wait for you :) Does this
> work?
Works for me too. Thanks, Ignasi! I guess that means that 1.7.x is
considered "frozen" until further notice for everyone except Ignasi..?
ap
Re: Bug Fix Release Date
Posted by Andrew Bayer <an...@gmail.com>.
Sounds good - I'll kick myself to the office fast enough to be on by 7am
PST (so 4pm CET). =)
A.
On Wed, Feb 5, 2014 at 12:31 PM, Ignasi Barrera <ig...@gmail.com>wrote:
> I'll cut the release tomorrow then and will include the DigitalOcean
> provider.
>
> I plan to start the release tomorrow at 9:00 AM (CET), which is in 12
> hours or so and if I get in trouble I'll wait for you :) Does this
> work?
>
> On 5 February 2014 21:09, Andrew Bayer <an...@gmail.com> wrote:
> > Ignasi, feel free to do it - I'll try to get online early tomorrow (by
> 7am
> > PST) in case you have problems.
> >
> > A.
> >
> >
> > On Wed, Feb 5, 2014 at 12:02 PM, Everett Toews
> > <ev...@rackspace.com>wrote:
> >
> >> I'm okay with DigitalOcean being included.
> >>
> >> I could also do the release (I haven't done one yet either) if you wind
> up
> >> not being able to Ignasi.
> >>
> >> Thanks,
> >> Everett
> >>
> >>
> >> On Feb 5, 2014, at 1:33 PM, Ignasi Barrera <ig...@gmail.com>
> >> wrote:
> >>
> >> > +1 to release with the workaround.
> >> >
> >> > I'd like to include the DigitalOcean one, as it is ready and already
> on
> >> > master. WDYT?
> >> >
> >> > I can do the release if my timezone works. I've not done an ASF
> release
> >> > yet, so perhaps I'm not as fast as others :) but I can do it.
> >> > El 05/02/2014 20:18, "Andrew Phillips" <ap...@qrmedia.com>
> escribió:
> >> >
> >> >> Yeah, I think we're ok for the workaround with 1.7.1. Let's do that
> >> ASAP.
> >> >>>
> >> >>
> >> >> Who can spin the wheels on this one? I'm afraid I'm stuck at an event
> >> all
> >> >> day tomorrow :-(
> >> >>
> >> >> Also: are there any other urgent PRs for 1.7.x we'd like to include
> >> here?
> >> >>
> >> >> ap
> >> >>
> >>
> >>
>
Re: Bug Fix Release Date
Posted by Ignasi Barrera <ig...@gmail.com>.
I'll cut the release tomorrow then and will include the DigitalOcean provider.
I plan to start the release tomorrow at 9:00 AM (CET), which is in 12
hours or so and if I get in trouble I'll wait for you :) Does this
work?
On 5 February 2014 21:09, Andrew Bayer <an...@gmail.com> wrote:
> Ignasi, feel free to do it - I'll try to get online early tomorrow (by 7am
> PST) in case you have problems.
>
> A.
>
>
> On Wed, Feb 5, 2014 at 12:02 PM, Everett Toews
> <ev...@rackspace.com>wrote:
>
>> I'm okay with DigitalOcean being included.
>>
>> I could also do the release (I haven't done one yet either) if you wind up
>> not being able to Ignasi.
>>
>> Thanks,
>> Everett
>>
>>
>> On Feb 5, 2014, at 1:33 PM, Ignasi Barrera <ig...@gmail.com>
>> wrote:
>>
>> > +1 to release with the workaround.
>> >
>> > I'd like to include the DigitalOcean one, as it is ready and already on
>> > master. WDYT?
>> >
>> > I can do the release if my timezone works. I've not done an ASF release
>> > yet, so perhaps I'm not as fast as others :) but I can do it.
>> > El 05/02/2014 20:18, "Andrew Phillips" <ap...@qrmedia.com> escribió:
>> >
>> >> Yeah, I think we're ok for the workaround with 1.7.1. Let's do that
>> ASAP.
>> >>>
>> >>
>> >> Who can spin the wheels on this one? I'm afraid I'm stuck at an event
>> all
>> >> day tomorrow :-(
>> >>
>> >> Also: are there any other urgent PRs for 1.7.x we'd like to include
>> here?
>> >>
>> >> ap
>> >>
>>
>>
Re: Bug Fix Release Date
Posted by Andrew Bayer <an...@gmail.com>.
Ignasi, feel free to do it - I'll try to get online early tomorrow (by 7am
PST) in case you have problems.
A.
On Wed, Feb 5, 2014 at 12:02 PM, Everett Toews
<ev...@rackspace.com>wrote:
> I'm okay with DigitalOcean being included.
>
> I could also do the release (I haven't done one yet either) if you wind up
> not being able to Ignasi.
>
> Thanks,
> Everett
>
>
> On Feb 5, 2014, at 1:33 PM, Ignasi Barrera <ig...@gmail.com>
> wrote:
>
> > +1 to release with the workaround.
> >
> > I'd like to include the DigitalOcean one, as it is ready and already on
> > master. WDYT?
> >
> > I can do the release if my timezone works. I've not done an ASF release
> > yet, so perhaps I'm not as fast as others :) but I can do it.
> > El 05/02/2014 20:18, "Andrew Phillips" <ap...@qrmedia.com> escribió:
> >
> >> Yeah, I think we're ok for the workaround with 1.7.1. Let's do that
> ASAP.
> >>>
> >>
> >> Who can spin the wheels on this one? I'm afraid I'm stuck at an event
> all
> >> day tomorrow :-(
> >>
> >> Also: are there any other urgent PRs for 1.7.x we'd like to include
> here?
> >>
> >> ap
> >>
>
>
Re: Bug Fix Release Date
Posted by Everett Toews <ev...@RACKSPACE.COM>.
I’m okay with DigitalOcean being included.
I could also do the release (I haven’t done one yet either) if you wind up not being able to Ignasi.
Thanks,
Everett
On Feb 5, 2014, at 1:33 PM, Ignasi Barrera <ig...@gmail.com> wrote:
> +1 to release with the workaround.
>
> I'd like to include the DigitalOcean one, as it is ready and already on
> master. WDYT?
>
> I can do the release if my timezone works. I've not done an ASF release
> yet, so perhaps I'm not as fast as others :) but I can do it.
> El 05/02/2014 20:18, "Andrew Phillips" <ap...@qrmedia.com> escribió:
>
>> Yeah, I think we're ok for the workaround with 1.7.1. Let's do that ASAP.
>>>
>>
>> Who can spin the wheels on this one? I'm afraid I'm stuck at an event all
>> day tomorrow :-(
>>
>> Also: are there any other urgent PRs for 1.7.x we'd like to include here?
>>
>> ap
>>
Re: Re: Bug Fix Release Date
Posted by Ignasi Barrera <ig...@gmail.com>.
+1 to release with the workaround.
I'd like to include the DigitalOcean one, as it is ready and already on
master. WDYT?
I can do the release if my timezone works. I've not done an ASF release
yet, so perhaps I'm not as fast as others :) but I can do it.
El 05/02/2014 20:18, "Andrew Phillips" <ap...@qrmedia.com> escribió:
> Yeah, I think we're ok for the workaround with 1.7.1. Let's do that ASAP.
>>
>
> Who can spin the wheels on this one? I'm afraid I'm stuck at an event all
> day tomorrow :-(
>
> Also: are there any other urgent PRs for 1.7.x we'd like to include here?
>
> ap
>
Re: Re: Bug Fix Release Date
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Yeah, I think we're ok for the workaround with 1.7.1. Let's do that ASAP.
Who can spin the wheels on this one? I'm afraid I'm stuck at an event
all day tomorrow :-(
Also: are there any other urgent PRs for 1.7.x we'd like to include here?
ap
Re: Re: Bug Fix Release Date
Posted by Andrew Bayer <an...@gmail.com>.
Yeah, I think we're ok for the workaround with 1.7.1. Let's do that ASAP.
A.
On Wed, Feb 5, 2014 at 10:58 AM, Andrew Phillips <ap...@qrmedia.com>wrote:
> Forwarding this to the dev@ list...
>
> TL;DR: Fine by me if we're OK to release with a workaround and without a
> fixed Guava version.
>
> This bug is really hurting our users. We need to stop the bleeding. Were
>> constantly asking users to use a snapshot release but what we really need
>> to do is give them a proper release with the workaround.
>>
>> I think we should do a 1.7.1 release as soon as possible.
>>
>
> Can do, as long as we're OK with the fact that the release will contain
> the workaround we had to apply. 1.7.x is still on Guava 15 and as far as I
> can see the Guava team has not released a patch for that (although there
> are users in the issue asking for that).
>
> Bumping 1.7.x to a different Guava version was "out of bounds" last I
> recall, as users have complained about the previously too.
>
> ap
>