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 2014/07/01 00:38:11 UTC
Re: [DISCUSS] The next version of jclouds
Thanks for breaking out some of our choices. I slightly prefer two
major releases to address Guava pain immediately and require Java 7
later. Would 1.8.x branch from 1.7.x or from master? If we branch from
master, we could delay the 2.0 release requiring Java 7 until later in
the year.
On Mon, Jun 30, 2014 at 09:18:20PM +0000, Everett Toews wrote:
> So we’ve reached consensus on moving to Java 7 in the next major release of jclouds [1].
>
> Jumping to 2.0 as our next release (due mid-July) is way too abrupt a change for our users. We need to give them some time to adapt and plan for it. 2 weeks is too short an amount of time for our users to digest this change, 2 months would be reasonable.
>
> Supposedly our next release should be 1.7.4 but, as Gaul pointed out in the other thread [1], many users are feeling the pain of us not upgrading Guava, which we only do in minor releases (e.g. the next Guava upgrade should happen in 1.8).
>
> So how about this?
>
> jclouds 1.8 (due mid-July) is our next version and the last version of jclouds to work with Java 6. We can also bump the Guava dep at this time.
>
> OR
>
> jclouds 1.7.4 (due mid-July) is our next version and the last version of jclouds to work with Java 6. We can also bump the Guava dep at this time.
>
> AND
>
> jclouds 2.0 (due early Sept.) is the first version of jclouds to work with Java 7.
>
> As of jclouds 2.0 we adopt the major release cadence (which we’re converging on).
>
> WDYT?
>
> Everett
>
> [1] http://jclouds.markmail.org/message/p2mmfvtnto3srpmq
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] The next version of jclouds
Posted by Andrew Gaul <ga...@apache.org>.
We have several potential tasks for 1.8.0:
1) streamline release process
2) Guava 18 compatibility (JCLOUDS-622)
3) reparent chef to core
I suspect we need another week to finish these tasks; I can finish 2 but
do we have owners for tasks 1 and 3? Given these outstanding tasks can
we plan for either 21 or 28 July? I can help on either of these dates.
On Fri, Jul 11, 2014 at 10:50:36PM +0000, Everett Toews wrote:
> When do we want to begin the release of 1.8.0?
>
> My preference is always to start it on a Monday or Tuesday so we can get it done by the end of the week but I’m open to whatever day. Let’s see how much we can automate during this release.
>
> abayer, we’ll likely need you available at some point as you mentioned you were able to get some automation done around the hellish entering of versions as the release happens.
>
> 1. Week of July 14.
>
> I’m totally unavailable on the 14th but available the rest of the week.
>
> 2. Week of July 21.
>
> I’m at OSCON this week and totally unavailable to help.
>
> 3. Week of July 28.
>
> I’m free.
>
>
> Thanks,
> Everett
>
>
> On Jul 1, 2014, at 12:00 PM, Everett Toews <ev...@rackspace.com> wrote:
>
> > On Jun 30, 2014, at 7:34 PM, Shrinand Javadekar <sh...@maginatics.com> wrote:
> >
> >> I was about to ask something similar. Is there a reason for having a
> >> 1.7.4 and a 1.8.0 release? Can't we simply do a 1.8.0 to alleviate the
> >> Guava pain and then do a v2.0 release?
> >
> > I should have parenthesized my proposal…
> >
> > ((1.7.4 xor 1.8.0) and then 2.0)
> >
> >> Also, IIRC one of the big ticket items in v2.0 was the graduation of
> >> the new openstack implementation from jclouds-labs to the main jclouds
> >> code. We should probably start that process sooner so that it gets as
> >> much testing as possible (and possibly bug fixes).
> >
> > Agreed. We would only have 2 months to get openstack-swift into production ready shape. I think it’s possible but we need to start now. WDYT?
> >
> > Everett
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] The next version of jclouds
Posted by Andrew Gaul <ga...@apache.org>.
On Fri, Jul 25, 2014 at 11:42:41PM +0000, Everett Toews wrote:
> Okay let’s begin the release on the 28th.
Thank you for managing this release! Good news, Roman Coedo made
sufficient progress on glacier that it is usable and we should ship it
in 1.8. However, the google-cloud-storage provider is not complete; can
you unhook it from pom.xml in the jclouds-labs-aws repository in the 1.8
branch? Finally I have concerns about openstack-swift integration test
failures; do you expect these results:
https://issues.apache.org/jira/browse/JCLOUDS-641
> I’ll kick things off around 11 am CDT (or whenever abayer is available :) and will be looking to IRC for help.
>
> I’ve opened a PR for the 1.8 release notes [1] directly on the Apache git repo so any committer can check it out and push commits. If you want me to change something I’ve written, feel free to comment. If you want to add something, please just add it.
Great, I will help with it this week.
> This will be the last release to support Java 6.
>
> The next release will be 2.0 and will happen in mid-September.
>
> If you disagree with any of the above, please say something now.
Agree on the last release to support Java 6, although prefer to defer
discussion of 2.0.
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] The next version of jclouds
Posted by Everett Toews <ev...@RACKSPACE.COM>.
Forgot to mention I added an “API Changes” section to the release notes. If you’re aware of any API changes (deprecations, API replacements, API removals), please add them there.
Thanks,
Everett
On Jul 25, 2014, at 6:42 PM, Everett Toews <ev...@rackspace.com> wrote:
> Okay let’s begin the release on the 28th.
>
> I’ll kick things off around 11 am CDT (or whenever abayer is available :) and will be looking to IRC for help.
>
> I’ve opened a PR for the 1.8 release notes [1] directly on the Apache git repo so any committer can check it out and push commits. If you want me to change something I’ve written, feel free to comment. If you want to add something, please just add it.
>
> This will be the last release to support Java 6.
>
> The next release will be 2.0 and will happen in mid-September.
>
> If you disagree with any of the above, please say something now.
>
> Thanks,
> Everett
>
> [1] https://github.com/jclouds/jclouds-site/pull/114
>
>
> On Jul 22, 2014, at 7:20 PM, Shrinand Javadekar <sh...@maginatics.com> wrote:
>
>> I'm open to help with the testing, specifically of the blobstores
>> portion next week (July 28th).
>>
>> On Fri, Jul 11, 2014 at 8:13 PM, Ignasi Barrera <na...@apache.org> wrote:
>>> I'll take the chef move and do it this next week. It should be pretty
>>> straightforward.
>>> El 12/07/2014 05:11, "Ignasi Barrera" <na...@apache.org> escribió:
>>>
>>>> I'll also be available those weeks
>>>> El 12/07/2014 01:43, "Andrew Phillips" <ap...@qrmedia.com> escribió:
>>>>
>>>>> 1. Week of July 14.
>>>>>>
>>>>>> I’m totally unavailable on the 14th but available the rest of the week.
>>>>>>
>>>>>> 2. Week of July 21.
>>>>>>
>>>>>> I’m at OSCON this week and totally unavailable to help.
>>>>>>
>>>>>> 3. Week of July 28.
>>>>>>
>>>>>> I’m free.
>>>>>>
>>>>>
>>>>> I should be able to help in the weeks of the 21st and 28th...
>>>>>
>>>>> ap
>>>>>
>>>>
>
Re: [DISCUSS] The next version of jclouds
Posted by Everett Toews <ev...@RACKSPACE.COM>.
Okay let’s begin the release on the 28th.
I’ll kick things off around 11 am CDT (or whenever abayer is available :) and will be looking to IRC for help.
I’ve opened a PR for the 1.8 release notes [1] directly on the Apache git repo so any committer can check it out and push commits. If you want me to change something I’ve written, feel free to comment. If you want to add something, please just add it.
This will be the last release to support Java 6.
The next release will be 2.0 and will happen in mid-September.
If you disagree with any of the above, please say something now.
Thanks,
Everett
[1] https://github.com/jclouds/jclouds-site/pull/114
On Jul 22, 2014, at 7:20 PM, Shrinand Javadekar <sh...@maginatics.com> wrote:
> I'm open to help with the testing, specifically of the blobstores
> portion next week (July 28th).
>
> On Fri, Jul 11, 2014 at 8:13 PM, Ignasi Barrera <na...@apache.org> wrote:
>> I'll take the chef move and do it this next week. It should be pretty
>> straightforward.
>> El 12/07/2014 05:11, "Ignasi Barrera" <na...@apache.org> escribió:
>>
>>> I'll also be available those weeks
>>> El 12/07/2014 01:43, "Andrew Phillips" <ap...@qrmedia.com> escribió:
>>>
>>>> 1. Week of July 14.
>>>>>
>>>>> I’m totally unavailable on the 14th but available the rest of the week.
>>>>>
>>>>> 2. Week of July 21.
>>>>>
>>>>> I’m at OSCON this week and totally unavailable to help.
>>>>>
>>>>> 3. Week of July 28.
>>>>>
>>>>> I’m free.
>>>>>
>>>>
>>>> I should be able to help in the weeks of the 21st and 28th...
>>>>
>>>> ap
>>>>
>>>
Re: [DISCUSS] The next version of jclouds
Posted by Shrinand Javadekar <sh...@maginatics.com>.
I'm open to help with the testing, specifically of the blobstores
portion next week (July 28th).
On Fri, Jul 11, 2014 at 8:13 PM, Ignasi Barrera <na...@apache.org> wrote:
> I'll take the chef move and do it this next week. It should be pretty
> straightforward.
> El 12/07/2014 05:11, "Ignasi Barrera" <na...@apache.org> escribió:
>
>> I'll also be available those weeks
>> El 12/07/2014 01:43, "Andrew Phillips" <ap...@qrmedia.com> escribió:
>>
>>> 1. Week of July 14.
>>>>
>>>> I’m totally unavailable on the 14th but available the rest of the week.
>>>>
>>>> 2. Week of July 21.
>>>>
>>>> I’m at OSCON this week and totally unavailable to help.
>>>>
>>>> 3. Week of July 28.
>>>>
>>>> I’m free.
>>>>
>>>
>>> I should be able to help in the weeks of the 21st and 28th...
>>>
>>> ap
>>>
>>
Re: [DISCUSS] The next version of jclouds
Posted by Ignasi Barrera <na...@apache.org>.
I'll take the chef move and do it this next week. It should be pretty
straightforward.
El 12/07/2014 05:11, "Ignasi Barrera" <na...@apache.org> escribió:
> I'll also be available those weeks
> El 12/07/2014 01:43, "Andrew Phillips" <ap...@qrmedia.com> escribió:
>
>> 1. Week of July 14.
>>>
>>> I’m totally unavailable on the 14th but available the rest of the week.
>>>
>>> 2. Week of July 21.
>>>
>>> I’m at OSCON this week and totally unavailable to help.
>>>
>>> 3. Week of July 28.
>>>
>>> I’m free.
>>>
>>
>> I should be able to help in the weeks of the 21st and 28th...
>>
>> ap
>>
>
Re: [DISCUSS] The next version of jclouds
Posted by Ignasi Barrera <na...@apache.org>.
I'll also be available those weeks
El 12/07/2014 01:43, "Andrew Phillips" <ap...@qrmedia.com> escribió:
> 1. Week of July 14.
>>
>> I’m totally unavailable on the 14th but available the rest of the week.
>>
>> 2. Week of July 21.
>>
>> I’m at OSCON this week and totally unavailable to help.
>>
>> 3. Week of July 28.
>>
>> I’m free.
>>
>
> I should be able to help in the weeks of the 21st and 28th...
>
> ap
>
Re: [DISCUSS] The next version of jclouds
Posted by Andrew Phillips <ap...@qrmedia.com>.
> 1. Week of July 14.
>
> I’m totally unavailable on the 14th but available the rest of the week.
>
> 2. Week of July 21.
>
> I’m at OSCON this week and totally unavailable to help.
>
> 3. Week of July 28.
>
> I’m free.
I should be able to help in the weeks of the 21st and 28th...
ap
Re: [DISCUSS] The next version of jclouds
Posted by Everett Toews <ev...@RACKSPACE.COM>.
When do we want to begin the release of 1.8.0?
My preference is always to start it on a Monday or Tuesday so we can get it done by the end of the week but I’m open to whatever day. Let’s see how much we can automate during this release.
abayer, we’ll likely need you available at some point as you mentioned you were able to get some automation done around the hellish entering of versions as the release happens.
1. Week of July 14.
I’m totally unavailable on the 14th but available the rest of the week.
2. Week of July 21.
I’m at OSCON this week and totally unavailable to help.
3. Week of July 28.
I’m free.
Thanks,
Everett
On Jul 1, 2014, at 12:00 PM, Everett Toews <ev...@rackspace.com> wrote:
> On Jun 30, 2014, at 7:34 PM, Shrinand Javadekar <sh...@maginatics.com> wrote:
>
>> I was about to ask something similar. Is there a reason for having a
>> 1.7.4 and a 1.8.0 release? Can't we simply do a 1.8.0 to alleviate the
>> Guava pain and then do a v2.0 release?
>
> I should have parenthesized my proposal…
>
> ((1.7.4 xor 1.8.0) and then 2.0)
>
>> Also, IIRC one of the big ticket items in v2.0 was the graduation of
>> the new openstack implementation from jclouds-labs to the main jclouds
>> code. We should probably start that process sooner so that it gets as
>> much testing as possible (and possibly bug fixes).
>
> Agreed. We would only have 2 months to get openstack-swift into production ready shape. I think it’s possible but we need to start now. WDYT?
>
> Everett
Re: [DISCUSS] The next version of jclouds
Posted by Everett Toews <ev...@RACKSPACE.COM>.
On Jun 30, 2014, at 7:34 PM, Shrinand Javadekar <sh...@maginatics.com> wrote:
> I was about to ask something similar. Is there a reason for having a
> 1.7.4 and a 1.8.0 release? Can't we simply do a 1.8.0 to alleviate the
> Guava pain and then do a v2.0 release?
I should have parenthesized my proposal…
((1.7.4 xor 1.8.0) and then 2.0)
> Also, IIRC one of the big ticket items in v2.0 was the graduation of
> the new openstack implementation from jclouds-labs to the main jclouds
> code. We should probably start that process sooner so that it gets as
> much testing as possible (and possibly bug fixes).
Agreed. We would only have 2 months to get openstack-swift into production ready shape. I think it’s possible but we need to start now. WDYT?
Everett
Re: [DISCUSS] The next version of jclouds
Posted by Shrinand Javadekar <sh...@maginatics.com>.
I was about to ask something similar. Is there a reason for having a
1.7.4 and a 1.8.0 release? Can't we simply do a 1.8.0 to alleviate the
Guava pain and then do a v2.0 release?
Also, IIRC one of the big ticket items in v2.0 was the graduation of
the new openstack implementation from jclouds-labs to the main jclouds
code. We should probably start that process sooner so that it gets as
much testing as possible (and possibly bug fixes).
-Shri
On Mon, Jun 30, 2014 at 5:10 PM, Andrew Phillips <ap...@qrmedia.com> wrote:
>>> So how about this?
>
>
> My preference would be for 1.8.0 with the latest Guava version, branching
> off master, being the next release, and the last to support Java 6.
>
> 2.0, coming in Sept, would be the first version to support Java 7 and up
> only.
>
> ap
Re: [DISCUSS] The next version of jclouds
Posted by Andrew Phillips <ap...@qrmedia.com>.
>> So how about this?
My preference would be for 1.8.0 with the latest Guava version,
branching off master, being the next release, and the last to support
Java 6.
2.0, coming in Sept, would be the first version to support Java 7 and up only.
ap