You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Zack Shoylev <za...@RACKSPACE.COM> on 2014/12/08 21:05:55 UTC
[DISCUSS] next release / roadmap
I wanted to start a discussion about getting the next release done. Here are some questions that we should discuss. Feel free to add more (what am I missing here?). This will also help us get on the same page.
1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
2. What should be the minimum included in it?
3. Can we get a release out by the end of December (considering holidays)?
Thanks,
Zack
Re: [DISCUSS] next release / roadmap
Posted by Andrew Phillips <ap...@qrmedia.com>.
> Nevertheless, let me know if there is anything I can do to help
> with the release this weekend, I will be available.
I should also be available on Sunday. Thanks, Ignasi!
Regards
ap
Re: [DISCUSS] next release / roadmap
Posted by Personal <ch...@gmail.com>.
+1 and I apologize that I have not been engaged with this discussion lately. Unfortunately, I’m working way too many hours on an iOS project that takes my mind far from the jclouds realm :-) Nevertheless, let me know if there is anything I can do to help with the release this weekend, I will be available.
CC
--
Chris Custine
From: Andrea Turli <an...@gmail.com>
Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
Date: March 11, 2015 at 2:26:18 AM
To: dev@jclouds.apache.org <de...@jclouds.apache.org>>, Ignasi Barrera <na...@apache.org>>
Subject: Re: [DISCUSS] next release / roadmap
+1
Thanks Ignasi
On Tue, Mar 10, 2015 at 11:11 PM Ignasi Barrera <na...@apache.org> wrote:
> There have been no responses, but several in this thread, including
> me, would like a release, so I'll cut the 1.9.0 release this weekend.
>
> On 27 February 2015 at 10:28, Ignasi Barrera <na...@apache.org> wrote:
> > +1.
> >
> > Given the time that has passed since we started the discussion, I think
> we
> > should cut the release sooner than later. My main worries where the AWS
> live
> > tests. I fixed half of the failing tests (all the ComputeService related
> > ones), and the remaining ones are api specific issues that I still
> haven't
> > had time to investigate. I wouldn't consider those blockers, though.
> >
> > So, shall we cut the release by the beginning of the next week?
> > I'll volunteer to do the release if no one has a especial interest in
> doing
> > it :)
> >
> >
> >
> > On 27 February 2015 at 00:13, Andrew Gaul <ga...@apache.org> wrote:
> >>
> >> Issues targeting the 1.9.0 release:
> >>
> >>
> >> https://issues.apache.org/jira/secure/IssueNavigator.
> jspa?reset=true&jqlQuery=project+%3D+JCLOUDS+AND+
> resolution+%3D+Unresolved+AND+fixVersion+%3D+1.9.0
> >>
> >> None of these seem like blocking issues to me. I strongly prefer to run
> >> a release as soon as possible as master has a number of important fixes.
> >>
> >> On Thu, Feb 26, 2015 at 02:59:27PM -0800, Daniel Broudy wrote:
> >> > Ping.
> >> >
> >> > A few questions:
> >> > What is the todo list?
> >> > What is the time frame we are working with?
> >> > Is there a Jira issue tracking this?
> >> >
> >> > I am excited for a new release!
> >> >
> >> > On Tue, Feb 3, 2015 at 3:43 PM, Ignasi Barrera <na...@apache.org>
> wrote:
> >> >
> >> > > Another quick update: I've started working on the aws-ec2 test
> >> > > failures and just opened: https://github.com/jclouds/
> jclouds/pull/664
> >> > > That fixes half the failing tests, and all the template builder
> >> > > related ones. I'll try to have all the rest fixed by the end of the
> >> > > week.
> >> > >
> >> > > On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org>
> wrote:
> >> > > > Also, JCLOUDS-104 [1] was in my checklist and fixing it should
> make
> >> > > > the release process less painful. I tried to summarize in my last
> >> > > > comment the remaining bits. Could someone have a look at it? We're
> >> > > > almost there! If there are no volunteers I'll take it once I'm
> done
> >> > > > with the AWS live tests.
> >> > > >
> >> > > >
> >> > > > [1] https://issues.apache.org/jira/browse/JCLOUDS-104
> >> > > >
> >> > > > On 2 February 2015 at 21:56, Ignasi Barrera
> >> > > > <ig...@gmail.com>
> >> > > wrote:
> >> > > >> Many thanks Zack!
> >> > > >>
> >> > > >> I've started to have a look at the aws-ec2 test failures and
> expect
> >> > > >> to
> >> > > >> work on them this week.
> >> > > >>
> >> > > >> On 31 January 2015 at 05:15, Zack Shoylev
> >> > > >> <za...@rackspace.com>
> >> > > wrote:
> >> > > >>> Quick update, I have now fixed the compute live test problems
> for
> >> > > cloudfiles-us.
> >> > > >>> ________________________________________
> >> > > >>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
> >> > > >>> Sent: Wednesday, January 28, 2015 11:13 AM
> >> > > >>> To: dev@jclouds.apache.org
> >> > > >>> Subject: RE: [DISCUSS] next release / roadmap
> >> > > >>>
> >> > > >>> Some good news, blobstore and compute for rackspace now are
> >> > > live-tested (thanks Everett) here:
> >> > > >>> https://jclouds.ci.cloudbees.com/view/live%20tests/
> >> > > >>>
> >> > > >>> Compute has 4 failures from what I see. Should be possible to
> >> > > >>> figure
> >> > > those out for next release.
> >> > > >>> From what I remember those are image OS related (such as OS
> >> > > >>> version
> >> > > mismatch).
> >> > > >>> Thanks!
> >> > > >>>
> >> > > >>> ________________________________________
> >> > > >>> From: Andrew Phillips [aphillips@qrmedia.com]
> >> > > >>> Sent: Tuesday, January 27, 2015 8:28 AM
> >> > > >>> To: dev@jclouds.apache.org
> >> > > >>> Subject: Re: [DISCUSS] next release / roadmap
> >> > > >>>
> >> > > >>>> There are failures in AWS compute (I'll volunteer to take a
> look
> >> > > >>>> at
> >> > > >>>> them), in the blobstore providers you mentioned, and there are
> >> > > >>>> also
> >> > > >>>> many failures in rackspace compute, that I've been reporting
> for
> >> > > >>>> several releases. Those failures should be addressed too in
> this
> >> > > >>>> release.
> >> > > >>>
> >> > > >>> As a first step, do we know whether we have issues in JIRA (with
> >> > > >>> the
> >> > > >>> correct fix version etc.) for all these issues? Then we can
> >> > > >>> hopefully
> >> > > >>> use JIRA as a "proper" backlog management tool for 1.9.0.
> >> > > >>>
> >> > > >>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
> >> > > >>>
> >> > > >>> Regards
> >> > > >>>
> >> > > >>> ap
> >> > > >>>
> >> > > >>> --
> >> > > >>> Andrew Phillips
> >> > > >>> qrmedia
> >> > > >>>
> >> > > >>> Unless expressly stated otherwise, this message is confidential.
> >> > > >>> Access to this e-mail by anyone else is unauthorised. If you are
> >> > > >>> not an addressee, any disclosure or copying of the contents of
> >> > > >>> this e-mail or any action taken (or not taken) in reliance on it
> >> > > >>> is unauthorised and may be unlawful. If you are not an
> addressee,
> >> > > >>> please inform the sender immediately.
> >> > > >>>
> >> > > >>> This message is confidential and may not be redistributed or
> >> > > >>> broadcast in whole or part in any form, including but not
> limited
> >> > > >>> to any form of internet transmission including email, usenet,
> >> > > >>> newsgroups, www, irc, icq, etc.
> >> > > >>> All liability for errors and viruses is disclaimed.
> >> > >
> >>
> >> --
> >> Andrew Gaul
> >> http://gaul.org/
> >
> >
>
Re: [DISCUSS] next release / roadmap
Posted by Andrea Turli <an...@gmail.com>.
+1
Thanks Ignasi
On Tue, Mar 10, 2015 at 11:11 PM Ignasi Barrera <na...@apache.org> wrote:
> There have been no responses, but several in this thread, including
> me, would like a release, so I'll cut the 1.9.0 release this weekend.
>
> On 27 February 2015 at 10:28, Ignasi Barrera <na...@apache.org> wrote:
> > +1.
> >
> > Given the time that has passed since we started the discussion, I think
> we
> > should cut the release sooner than later. My main worries where the AWS
> live
> > tests. I fixed half of the failing tests (all the ComputeService related
> > ones), and the remaining ones are api specific issues that I still
> haven't
> > had time to investigate. I wouldn't consider those blockers, though.
> >
> > So, shall we cut the release by the beginning of the next week?
> > I'll volunteer to do the release if no one has a especial interest in
> doing
> > it :)
> >
> >
> >
> > On 27 February 2015 at 00:13, Andrew Gaul <ga...@apache.org> wrote:
> >>
> >> Issues targeting the 1.9.0 release:
> >>
> >>
> >> https://issues.apache.org/jira/secure/IssueNavigator.
> jspa?reset=true&jqlQuery=project+%3D+JCLOUDS+AND+
> resolution+%3D+Unresolved+AND+fixVersion+%3D+1.9.0
> >>
> >> None of these seem like blocking issues to me. I strongly prefer to run
> >> a release as soon as possible as master has a number of important fixes.
> >>
> >> On Thu, Feb 26, 2015 at 02:59:27PM -0800, Daniel Broudy wrote:
> >> > Ping.
> >> >
> >> > A few questions:
> >> > What is the todo list?
> >> > What is the time frame we are working with?
> >> > Is there a Jira issue tracking this?
> >> >
> >> > I am excited for a new release!
> >> >
> >> > On Tue, Feb 3, 2015 at 3:43 PM, Ignasi Barrera <na...@apache.org>
> wrote:
> >> >
> >> > > Another quick update: I've started working on the aws-ec2 test
> >> > > failures and just opened: https://github.com/jclouds/
> jclouds/pull/664
> >> > > That fixes half the failing tests, and all the template builder
> >> > > related ones. I'll try to have all the rest fixed by the end of the
> >> > > week.
> >> > >
> >> > > On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org>
> wrote:
> >> > > > Also, JCLOUDS-104 [1] was in my checklist and fixing it should
> make
> >> > > > the release process less painful. I tried to summarize in my last
> >> > > > comment the remaining bits. Could someone have a look at it? We're
> >> > > > almost there! If there are no volunteers I'll take it once I'm
> done
> >> > > > with the AWS live tests.
> >> > > >
> >> > > >
> >> > > > [1] https://issues.apache.org/jira/browse/JCLOUDS-104
> >> > > >
> >> > > > On 2 February 2015 at 21:56, Ignasi Barrera
> >> > > > <ig...@gmail.com>
> >> > > wrote:
> >> > > >> Many thanks Zack!
> >> > > >>
> >> > > >> I've started to have a look at the aws-ec2 test failures and
> expect
> >> > > >> to
> >> > > >> work on them this week.
> >> > > >>
> >> > > >> On 31 January 2015 at 05:15, Zack Shoylev
> >> > > >> <za...@rackspace.com>
> >> > > wrote:
> >> > > >>> Quick update, I have now fixed the compute live test problems
> for
> >> > > cloudfiles-us.
> >> > > >>> ________________________________________
> >> > > >>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
> >> > > >>> Sent: Wednesday, January 28, 2015 11:13 AM
> >> > > >>> To: dev@jclouds.apache.org
> >> > > >>> Subject: RE: [DISCUSS] next release / roadmap
> >> > > >>>
> >> > > >>> Some good news, blobstore and compute for rackspace now are
> >> > > live-tested (thanks Everett) here:
> >> > > >>> https://jclouds.ci.cloudbees.com/view/live%20tests/
> >> > > >>>
> >> > > >>> Compute has 4 failures from what I see. Should be possible to
> >> > > >>> figure
> >> > > those out for next release.
> >> > > >>> From what I remember those are image OS related (such as OS
> >> > > >>> version
> >> > > mismatch).
> >> > > >>> Thanks!
> >> > > >>>
> >> > > >>> ________________________________________
> >> > > >>> From: Andrew Phillips [aphillips@qrmedia.com]
> >> > > >>> Sent: Tuesday, January 27, 2015 8:28 AM
> >> > > >>> To: dev@jclouds.apache.org
> >> > > >>> Subject: Re: [DISCUSS] next release / roadmap
> >> > > >>>
> >> > > >>>> There are failures in AWS compute (I'll volunteer to take a
> look
> >> > > >>>> at
> >> > > >>>> them), in the blobstore providers you mentioned, and there are
> >> > > >>>> also
> >> > > >>>> many failures in rackspace compute, that I've been reporting
> for
> >> > > >>>> several releases. Those failures should be addressed too in
> this
> >> > > >>>> release.
> >> > > >>>
> >> > > >>> As a first step, do we know whether we have issues in JIRA (with
> >> > > >>> the
> >> > > >>> correct fix version etc.) for all these issues? Then we can
> >> > > >>> hopefully
> >> > > >>> use JIRA as a "proper" backlog management tool for 1.9.0.
> >> > > >>>
> >> > > >>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
> >> > > >>>
> >> > > >>> Regards
> >> > > >>>
> >> > > >>> ap
> >> > > >>>
> >> > > >>> --
> >> > > >>> Andrew Phillips
> >> > > >>> qrmedia
> >> > > >>>
> >> > > >>> Unless expressly stated otherwise, this message is confidential.
> >> > > >>> Access to this e-mail by anyone else is unauthorised. If you are
> >> > > >>> not an addressee, any disclosure or copying of the contents of
> >> > > >>> this e-mail or any action taken (or not taken) in reliance on it
> >> > > >>> is unauthorised and may be unlawful. If you are not an
> addressee,
> >> > > >>> please inform the sender immediately.
> >> > > >>>
> >> > > >>> This message is confidential and may not be redistributed or
> >> > > >>> broadcast in whole or part in any form, including but not
> limited
> >> > > >>> to any form of internet transmission including email, usenet,
> >> > > >>> newsgroups, www, irc, icq, etc.
> >> > > >>> All liability for errors and viruses is disclaimed.
> >> > >
> >>
> >> --
> >> Andrew Gaul
> >> http://gaul.org/
> >
> >
>
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <na...@apache.org>.
There have been no responses, but several in this thread, including
me, would like a release, so I'll cut the 1.9.0 release this weekend.
On 27 February 2015 at 10:28, Ignasi Barrera <na...@apache.org> wrote:
> +1.
>
> Given the time that has passed since we started the discussion, I think we
> should cut the release sooner than later. My main worries where the AWS live
> tests. I fixed half of the failing tests (all the ComputeService related
> ones), and the remaining ones are api specific issues that I still haven't
> had time to investigate. I wouldn't consider those blockers, though.
>
> So, shall we cut the release by the beginning of the next week?
> I'll volunteer to do the release if no one has a especial interest in doing
> it :)
>
>
>
> On 27 February 2015 at 00:13, Andrew Gaul <ga...@apache.org> wrote:
>>
>> Issues targeting the 1.9.0 release:
>>
>>
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JCLOUDS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+1.9.0
>>
>> None of these seem like blocking issues to me. I strongly prefer to run
>> a release as soon as possible as master has a number of important fixes.
>>
>> On Thu, Feb 26, 2015 at 02:59:27PM -0800, Daniel Broudy wrote:
>> > Ping.
>> >
>> > A few questions:
>> > What is the todo list?
>> > What is the time frame we are working with?
>> > Is there a Jira issue tracking this?
>> >
>> > I am excited for a new release!
>> >
>> > On Tue, Feb 3, 2015 at 3:43 PM, Ignasi Barrera <na...@apache.org> wrote:
>> >
>> > > Another quick update: I've started working on the aws-ec2 test
>> > > failures and just opened: https://github.com/jclouds/jclouds/pull/664
>> > > That fixes half the failing tests, and all the template builder
>> > > related ones. I'll try to have all the rest fixed by the end of the
>> > > week.
>> > >
>> > > On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org> wrote:
>> > > > Also, JCLOUDS-104 [1] was in my checklist and fixing it should make
>> > > > the release process less painful. I tried to summarize in my last
>> > > > comment the remaining bits. Could someone have a look at it? We're
>> > > > almost there! If there are no volunteers I'll take it once I'm done
>> > > > with the AWS live tests.
>> > > >
>> > > >
>> > > > [1] https://issues.apache.org/jira/browse/JCLOUDS-104
>> > > >
>> > > > On 2 February 2015 at 21:56, Ignasi Barrera
>> > > > <ig...@gmail.com>
>> > > wrote:
>> > > >> Many thanks Zack!
>> > > >>
>> > > >> I've started to have a look at the aws-ec2 test failures and expect
>> > > >> to
>> > > >> work on them this week.
>> > > >>
>> > > >> On 31 January 2015 at 05:15, Zack Shoylev
>> > > >> <za...@rackspace.com>
>> > > wrote:
>> > > >>> Quick update, I have now fixed the compute live test problems for
>> > > cloudfiles-us.
>> > > >>> ________________________________________
>> > > >>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
>> > > >>> Sent: Wednesday, January 28, 2015 11:13 AM
>> > > >>> To: dev@jclouds.apache.org
>> > > >>> Subject: RE: [DISCUSS] next release / roadmap
>> > > >>>
>> > > >>> Some good news, blobstore and compute for rackspace now are
>> > > live-tested (thanks Everett) here:
>> > > >>> https://jclouds.ci.cloudbees.com/view/live%20tests/
>> > > >>>
>> > > >>> Compute has 4 failures from what I see. Should be possible to
>> > > >>> figure
>> > > those out for next release.
>> > > >>> From what I remember those are image OS related (such as OS
>> > > >>> version
>> > > mismatch).
>> > > >>> Thanks!
>> > > >>>
>> > > >>> ________________________________________
>> > > >>> From: Andrew Phillips [aphillips@qrmedia.com]
>> > > >>> Sent: Tuesday, January 27, 2015 8:28 AM
>> > > >>> To: dev@jclouds.apache.org
>> > > >>> Subject: Re: [DISCUSS] next release / roadmap
>> > > >>>
>> > > >>>> There are failures in AWS compute (I'll volunteer to take a look
>> > > >>>> at
>> > > >>>> them), in the blobstore providers you mentioned, and there are
>> > > >>>> also
>> > > >>>> many failures in rackspace compute, that I've been reporting for
>> > > >>>> several releases. Those failures should be addressed too in this
>> > > >>>> release.
>> > > >>>
>> > > >>> As a first step, do we know whether we have issues in JIRA (with
>> > > >>> the
>> > > >>> correct fix version etc.) for all these issues? Then we can
>> > > >>> hopefully
>> > > >>> use JIRA as a "proper" backlog management tool for 1.9.0.
>> > > >>>
>> > > >>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
>> > > >>>
>> > > >>> Regards
>> > > >>>
>> > > >>> ap
>> > > >>>
>> > > >>> --
>> > > >>> Andrew Phillips
>> > > >>> qrmedia
>> > > >>>
>> > > >>> Unless expressly stated otherwise, this message is confidential.
>> > > >>> Access to this e-mail by anyone else is unauthorised. If you are
>> > > >>> not an addressee, any disclosure or copying of the contents of
>> > > >>> this e-mail or any action taken (or not taken) in reliance on it
>> > > >>> is unauthorised and may be unlawful. If you are not an addressee,
>> > > >>> please inform the sender immediately.
>> > > >>>
>> > > >>> This message is confidential and may not be redistributed or
>> > > >>> broadcast in whole or part in any form, including but not limited
>> > > >>> to any form of internet transmission including email, usenet,
>> > > >>> newsgroups, www, irc, icq, etc.
>> > > >>> All liability for errors and viruses is disclaimed.
>> > >
>>
>> --
>> Andrew Gaul
>> http://gaul.org/
>
>
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <na...@apache.org>.
+1.
Given the time that has passed since we started the discussion, I think we
should cut the release sooner than later. My main worries where the AWS
live tests. I fixed half of the failing tests (all the ComputeService
related ones), and the remaining ones are api specific issues that I still
haven't had time to investigate. I wouldn't consider those blockers, though.
So, shall we cut the release by the beginning of the next week?
I'll volunteer to do the release if no one has a especial interest in doing
it :)
On 27 February 2015 at 00:13, Andrew Gaul <ga...@apache.org> wrote:
> Issues targeting the 1.9.0 release:
>
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JCLOUDS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+1.9.0
>
> None of these seem like blocking issues to me. I strongly prefer to run
> a release as soon as possible as master has a number of important fixes.
>
> On Thu, Feb 26, 2015 at 02:59:27PM -0800, Daniel Broudy wrote:
> > Ping.
> >
> > A few questions:
> > What is the todo list?
> > What is the time frame we are working with?
> > Is there a Jira issue tracking this?
> >
> > I am excited for a new release!
> >
> > On Tue, Feb 3, 2015 at 3:43 PM, Ignasi Barrera <na...@apache.org> wrote:
> >
> > > Another quick update: I've started working on the aws-ec2 test
> > > failures and just opened: https://github.com/jclouds/jclouds/pull/664
> > > That fixes half the failing tests, and all the template builder
> > > related ones. I'll try to have all the rest fixed by the end of the
> > > week.
> > >
> > > On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org> wrote:
> > > > Also, JCLOUDS-104 [1] was in my checklist and fixing it should make
> > > > the release process less painful. I tried to summarize in my last
> > > > comment the remaining bits. Could someone have a look at it? We're
> > > > almost there! If there are no volunteers I'll take it once I'm done
> > > > with the AWS live tests.
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/JCLOUDS-104
> > > >
> > > > On 2 February 2015 at 21:56, Ignasi Barrera <
> ignasi.barrera@gmail.com>
> > > wrote:
> > > >> Many thanks Zack!
> > > >>
> > > >> I've started to have a look at the aws-ec2 test failures and expect
> to
> > > >> work on them this week.
> > > >>
> > > >> On 31 January 2015 at 05:15, Zack Shoylev <
> zack.shoylev@rackspace.com>
> > > wrote:
> > > >>> Quick update, I have now fixed the compute live test problems for
> > > cloudfiles-us.
> > > >>> ________________________________________
> > > >>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
> > > >>> Sent: Wednesday, January 28, 2015 11:13 AM
> > > >>> To: dev@jclouds.apache.org
> > > >>> Subject: RE: [DISCUSS] next release / roadmap
> > > >>>
> > > >>> Some good news, blobstore and compute for rackspace now are
> > > live-tested (thanks Everett) here:
> > > >>> https://jclouds.ci.cloudbees.com/view/live%20tests/
> > > >>>
> > > >>> Compute has 4 failures from what I see. Should be possible to
> figure
> > > those out for next release.
> > > >>> From what I remember those are image OS related (such as OS version
> > > mismatch).
> > > >>> Thanks!
> > > >>>
> > > >>> ________________________________________
> > > >>> From: Andrew Phillips [aphillips@qrmedia.com]
> > > >>> Sent: Tuesday, January 27, 2015 8:28 AM
> > > >>> To: dev@jclouds.apache.org
> > > >>> Subject: Re: [DISCUSS] next release / roadmap
> > > >>>
> > > >>>> There are failures in AWS compute (I'll volunteer to take a look
> at
> > > >>>> them), in the blobstore providers you mentioned, and there are
> also
> > > >>>> many failures in rackspace compute, that I've been reporting for
> > > >>>> several releases. Those failures should be addressed too in this
> > > >>>> release.
> > > >>>
> > > >>> As a first step, do we know whether we have issues in JIRA (with
> the
> > > >>> correct fix version etc.) for all these issues? Then we can
> hopefully
> > > >>> use JIRA as a "proper" backlog management tool for 1.9.0.
> > > >>>
> > > >>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
> > > >>>
> > > >>> Regards
> > > >>>
> > > >>> ap
> > > >>>
> > > >>> --
> > > >>> Andrew Phillips
> > > >>> qrmedia
> > > >>>
> > > >>> Unless expressly stated otherwise, this message is confidential.
> > > >>> Access to this e-mail by anyone else is unauthorised. If you are
> > > >>> not an addressee, any disclosure or copying of the contents of
> > > >>> this e-mail or any action taken (or not taken) in reliance on it
> > > >>> is unauthorised and may be unlawful. If you are not an addressee,
> > > >>> please inform the sender immediately.
> > > >>>
> > > >>> This message is confidential and may not be redistributed or
> > > >>> broadcast in whole or part in any form, including but not limited
> > > >>> to any form of internet transmission including email, usenet,
> > > >>> newsgroups, www, irc, icq, etc.
> > > >>> All liability for errors and viruses is disclaimed.
> > >
>
> --
> Andrew Gaul
> http://gaul.org/
>
Re: [DISCUSS] next release / roadmap
Posted by Andrew Gaul <ga...@apache.org>.
Issues targeting the 1.9.0 release:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JCLOUDS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+1.9.0
None of these seem like blocking issues to me. I strongly prefer to run
a release as soon as possible as master has a number of important fixes.
On Thu, Feb 26, 2015 at 02:59:27PM -0800, Daniel Broudy wrote:
> Ping.
>
> A few questions:
> What is the todo list?
> What is the time frame we are working with?
> Is there a Jira issue tracking this?
>
> I am excited for a new release!
>
> On Tue, Feb 3, 2015 at 3:43 PM, Ignasi Barrera <na...@apache.org> wrote:
>
> > Another quick update: I've started working on the aws-ec2 test
> > failures and just opened: https://github.com/jclouds/jclouds/pull/664
> > That fixes half the failing tests, and all the template builder
> > related ones. I'll try to have all the rest fixed by the end of the
> > week.
> >
> > On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org> wrote:
> > > Also, JCLOUDS-104 [1] was in my checklist and fixing it should make
> > > the release process less painful. I tried to summarize in my last
> > > comment the remaining bits. Could someone have a look at it? We're
> > > almost there! If there are no volunteers I'll take it once I'm done
> > > with the AWS live tests.
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/JCLOUDS-104
> > >
> > > On 2 February 2015 at 21:56, Ignasi Barrera <ig...@gmail.com>
> > wrote:
> > >> Many thanks Zack!
> > >>
> > >> I've started to have a look at the aws-ec2 test failures and expect to
> > >> work on them this week.
> > >>
> > >> On 31 January 2015 at 05:15, Zack Shoylev <za...@rackspace.com>
> > wrote:
> > >>> Quick update, I have now fixed the compute live test problems for
> > cloudfiles-us.
> > >>> ________________________________________
> > >>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
> > >>> Sent: Wednesday, January 28, 2015 11:13 AM
> > >>> To: dev@jclouds.apache.org
> > >>> Subject: RE: [DISCUSS] next release / roadmap
> > >>>
> > >>> Some good news, blobstore and compute for rackspace now are
> > live-tested (thanks Everett) here:
> > >>> https://jclouds.ci.cloudbees.com/view/live%20tests/
> > >>>
> > >>> Compute has 4 failures from what I see. Should be possible to figure
> > those out for next release.
> > >>> From what I remember those are image OS related (such as OS version
> > mismatch).
> > >>> Thanks!
> > >>>
> > >>> ________________________________________
> > >>> From: Andrew Phillips [aphillips@qrmedia.com]
> > >>> Sent: Tuesday, January 27, 2015 8:28 AM
> > >>> To: dev@jclouds.apache.org
> > >>> Subject: Re: [DISCUSS] next release / roadmap
> > >>>
> > >>>> There are failures in AWS compute (I'll volunteer to take a look at
> > >>>> them), in the blobstore providers you mentioned, and there are also
> > >>>> many failures in rackspace compute, that I've been reporting for
> > >>>> several releases. Those failures should be addressed too in this
> > >>>> release.
> > >>>
> > >>> As a first step, do we know whether we have issues in JIRA (with the
> > >>> correct fix version etc.) for all these issues? Then we can hopefully
> > >>> use JIRA as a "proper" backlog management tool for 1.9.0.
> > >>>
> > >>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
> > >>>
> > >>> Regards
> > >>>
> > >>> ap
> > >>>
> > >>> --
> > >>> Andrew Phillips
> > >>> qrmedia
> > >>>
> > >>> Unless expressly stated otherwise, this message is confidential.
> > >>> Access to this e-mail by anyone else is unauthorised. If you are
> > >>> not an addressee, any disclosure or copying of the contents of
> > >>> this e-mail or any action taken (or not taken) in reliance on it
> > >>> is unauthorised and may be unlawful. If you are not an addressee,
> > >>> please inform the sender immediately.
> > >>>
> > >>> This message is confidential and may not be redistributed or
> > >>> broadcast in whole or part in any form, including but not limited
> > >>> to any form of internet transmission including email, usenet,
> > >>> newsgroups, www, irc, icq, etc.
> > >>> All liability for errors and viruses is disclaimed.
> >
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] next release / roadmap
Posted by Daniel Broudy <br...@google.com>.
Ping.
A few questions:
What is the todo list?
What is the time frame we are working with?
Is there a Jira issue tracking this?
I am excited for a new release!
On Tue, Feb 3, 2015 at 3:43 PM, Ignasi Barrera <na...@apache.org> wrote:
> Another quick update: I've started working on the aws-ec2 test
> failures and just opened: https://github.com/jclouds/jclouds/pull/664
> That fixes half the failing tests, and all the template builder
> related ones. I'll try to have all the rest fixed by the end of the
> week.
>
> On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org> wrote:
> > Also, JCLOUDS-104 [1] was in my checklist and fixing it should make
> > the release process less painful. I tried to summarize in my last
> > comment the remaining bits. Could someone have a look at it? We're
> > almost there! If there are no volunteers I'll take it once I'm done
> > with the AWS live tests.
> >
> >
> > [1] https://issues.apache.org/jira/browse/JCLOUDS-104
> >
> > On 2 February 2015 at 21:56, Ignasi Barrera <ig...@gmail.com>
> wrote:
> >> Many thanks Zack!
> >>
> >> I've started to have a look at the aws-ec2 test failures and expect to
> >> work on them this week.
> >>
> >> On 31 January 2015 at 05:15, Zack Shoylev <za...@rackspace.com>
> wrote:
> >>> Quick update, I have now fixed the compute live test problems for
> cloudfiles-us.
> >>> ________________________________________
> >>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
> >>> Sent: Wednesday, January 28, 2015 11:13 AM
> >>> To: dev@jclouds.apache.org
> >>> Subject: RE: [DISCUSS] next release / roadmap
> >>>
> >>> Some good news, blobstore and compute for rackspace now are
> live-tested (thanks Everett) here:
> >>> https://jclouds.ci.cloudbees.com/view/live%20tests/
> >>>
> >>> Compute has 4 failures from what I see. Should be possible to figure
> those out for next release.
> >>> From what I remember those are image OS related (such as OS version
> mismatch).
> >>> Thanks!
> >>>
> >>> ________________________________________
> >>> From: Andrew Phillips [aphillips@qrmedia.com]
> >>> Sent: Tuesday, January 27, 2015 8:28 AM
> >>> To: dev@jclouds.apache.org
> >>> Subject: Re: [DISCUSS] next release / roadmap
> >>>
> >>>> There are failures in AWS compute (I'll volunteer to take a look at
> >>>> them), in the blobstore providers you mentioned, and there are also
> >>>> many failures in rackspace compute, that I've been reporting for
> >>>> several releases. Those failures should be addressed too in this
> >>>> release.
> >>>
> >>> As a first step, do we know whether we have issues in JIRA (with the
> >>> correct fix version etc.) for all these issues? Then we can hopefully
> >>> use JIRA as a "proper" backlog management tool for 1.9.0.
> >>>
> >>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
> >>>
> >>> Regards
> >>>
> >>> ap
> >>>
> >>> --
> >>> Andrew Phillips
> >>> qrmedia
> >>>
> >>> Unless expressly stated otherwise, this message is confidential.
> >>> Access to this e-mail by anyone else is unauthorised. If you are
> >>> not an addressee, any disclosure or copying of the contents of
> >>> this e-mail or any action taken (or not taken) in reliance on it
> >>> is unauthorised and may be unlawful. If you are not an addressee,
> >>> please inform the sender immediately.
> >>>
> >>> This message is confidential and may not be redistributed or
> >>> broadcast in whole or part in any form, including but not limited
> >>> to any form of internet transmission including email, usenet,
> >>> newsgroups, www, irc, icq, etc.
> >>> All liability for errors and viruses is disclaimed.
>
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <na...@apache.org>.
Another quick update: I've started working on the aws-ec2 test
failures and just opened: https://github.com/jclouds/jclouds/pull/664
That fixes half the failing tests, and all the template builder
related ones. I'll try to have all the rest fixed by the end of the
week.
On 2 February 2015 at 21:59, Ignasi Barrera <na...@apache.org> wrote:
> Also, JCLOUDS-104 [1] was in my checklist and fixing it should make
> the release process less painful. I tried to summarize in my last
> comment the remaining bits. Could someone have a look at it? We're
> almost there! If there are no volunteers I'll take it once I'm done
> with the AWS live tests.
>
>
> [1] https://issues.apache.org/jira/browse/JCLOUDS-104
>
> On 2 February 2015 at 21:56, Ignasi Barrera <ig...@gmail.com> wrote:
>> Many thanks Zack!
>>
>> I've started to have a look at the aws-ec2 test failures and expect to
>> work on them this week.
>>
>> On 31 January 2015 at 05:15, Zack Shoylev <za...@rackspace.com> wrote:
>>> Quick update, I have now fixed the compute live test problems for cloudfiles-us.
>>> ________________________________________
>>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
>>> Sent: Wednesday, January 28, 2015 11:13 AM
>>> To: dev@jclouds.apache.org
>>> Subject: RE: [DISCUSS] next release / roadmap
>>>
>>> Some good news, blobstore and compute for rackspace now are live-tested (thanks Everett) here:
>>> https://jclouds.ci.cloudbees.com/view/live%20tests/
>>>
>>> Compute has 4 failures from what I see. Should be possible to figure those out for next release.
>>> From what I remember those are image OS related (such as OS version mismatch).
>>> Thanks!
>>>
>>> ________________________________________
>>> From: Andrew Phillips [aphillips@qrmedia.com]
>>> Sent: Tuesday, January 27, 2015 8:28 AM
>>> To: dev@jclouds.apache.org
>>> Subject: Re: [DISCUSS] next release / roadmap
>>>
>>>> There are failures in AWS compute (I'll volunteer to take a look at
>>>> them), in the blobstore providers you mentioned, and there are also
>>>> many failures in rackspace compute, that I've been reporting for
>>>> several releases. Those failures should be addressed too in this
>>>> release.
>>>
>>> As a first step, do we know whether we have issues in JIRA (with the
>>> correct fix version etc.) for all these issues? Then we can hopefully
>>> use JIRA as a "proper" backlog management tool for 1.9.0.
>>>
>>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
>>>
>>> Regards
>>>
>>> ap
>>>
>>> --
>>> Andrew Phillips
>>> qrmedia
>>>
>>> Unless expressly stated otherwise, this message is confidential.
>>> Access to this e-mail by anyone else is unauthorised. If you are
>>> not an addressee, any disclosure or copying of the contents of
>>> this e-mail or any action taken (or not taken) in reliance on it
>>> is unauthorised and may be unlawful. If you are not an addressee,
>>> please inform the sender immediately.
>>>
>>> This message is confidential and may not be redistributed or
>>> broadcast in whole or part in any form, including but not limited
>>> to any form of internet transmission including email, usenet,
>>> newsgroups, www, irc, icq, etc.
>>> All liability for errors and viruses is disclaimed.
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <na...@apache.org>.
Also, JCLOUDS-104 [1] was in my checklist and fixing it should make
the release process less painful. I tried to summarize in my last
comment the remaining bits. Could someone have a look at it? We're
almost there! If there are no volunteers I'll take it once I'm done
with the AWS live tests.
[1] https://issues.apache.org/jira/browse/JCLOUDS-104
On 2 February 2015 at 21:56, Ignasi Barrera <ig...@gmail.com> wrote:
> Many thanks Zack!
>
> I've started to have a look at the aws-ec2 test failures and expect to
> work on them this week.
>
> On 31 January 2015 at 05:15, Zack Shoylev <za...@rackspace.com> wrote:
>> Quick update, I have now fixed the compute live test problems for cloudfiles-us.
>> ________________________________________
>> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
>> Sent: Wednesday, January 28, 2015 11:13 AM
>> To: dev@jclouds.apache.org
>> Subject: RE: [DISCUSS] next release / roadmap
>>
>> Some good news, blobstore and compute for rackspace now are live-tested (thanks Everett) here:
>> https://jclouds.ci.cloudbees.com/view/live%20tests/
>>
>> Compute has 4 failures from what I see. Should be possible to figure those out for next release.
>> From what I remember those are image OS related (such as OS version mismatch).
>> Thanks!
>>
>> ________________________________________
>> From: Andrew Phillips [aphillips@qrmedia.com]
>> Sent: Tuesday, January 27, 2015 8:28 AM
>> To: dev@jclouds.apache.org
>> Subject: Re: [DISCUSS] next release / roadmap
>>
>>> There are failures in AWS compute (I'll volunteer to take a look at
>>> them), in the blobstore providers you mentioned, and there are also
>>> many failures in rackspace compute, that I've been reporting for
>>> several releases. Those failures should be addressed too in this
>>> release.
>>
>> As a first step, do we know whether we have issues in JIRA (with the
>> correct fix version etc.) for all these issues? Then we can hopefully
>> use JIRA as a "proper" backlog management tool for 1.9.0.
>>
>> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
>>
>> Regards
>>
>> ap
>>
>> --
>> Andrew Phillips
>> qrmedia
>>
>> Unless expressly stated otherwise, this message is confidential.
>> Access to this e-mail by anyone else is unauthorised. If you are
>> not an addressee, any disclosure or copying of the contents of
>> this e-mail or any action taken (or not taken) in reliance on it
>> is unauthorised and may be unlawful. If you are not an addressee,
>> please inform the sender immediately.
>>
>> This message is confidential and may not be redistributed or
>> broadcast in whole or part in any form, including but not limited
>> to any form of internet transmission including email, usenet,
>> newsgroups, www, irc, icq, etc.
>> All liability for errors and viruses is disclaimed.
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <ig...@gmail.com>.
Many thanks Zack!
I've started to have a look at the aws-ec2 test failures and expect to
work on them this week.
On 31 January 2015 at 05:15, Zack Shoylev <za...@rackspace.com> wrote:
> Quick update, I have now fixed the compute live test problems for cloudfiles-us.
> ________________________________________
> From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
> Sent: Wednesday, January 28, 2015 11:13 AM
> To: dev@jclouds.apache.org
> Subject: RE: [DISCUSS] next release / roadmap
>
> Some good news, blobstore and compute for rackspace now are live-tested (thanks Everett) here:
> https://jclouds.ci.cloudbees.com/view/live%20tests/
>
> Compute has 4 failures from what I see. Should be possible to figure those out for next release.
> From what I remember those are image OS related (such as OS version mismatch).
> Thanks!
>
> ________________________________________
> From: Andrew Phillips [aphillips@qrmedia.com]
> Sent: Tuesday, January 27, 2015 8:28 AM
> To: dev@jclouds.apache.org
> Subject: Re: [DISCUSS] next release / roadmap
>
>> There are failures in AWS compute (I'll volunteer to take a look at
>> them), in the blobstore providers you mentioned, and there are also
>> many failures in rackspace compute, that I've been reporting for
>> several releases. Those failures should be addressed too in this
>> release.
>
> As a first step, do we know whether we have issues in JIRA (with the
> correct fix version etc.) for all these issues? Then we can hopefully
> use JIRA as a "proper" backlog management tool for 1.9.0.
>
> Thanks for the JIRA cleanup work, Andrew G and Jeremy!
>
> Regards
>
> ap
>
> --
> Andrew Phillips
> qrmedia
>
> Unless expressly stated otherwise, this message is confidential.
> Access to this e-mail by anyone else is unauthorised. If you are
> not an addressee, any disclosure or copying of the contents of
> this e-mail or any action taken (or not taken) in reliance on it
> is unauthorised and may be unlawful. If you are not an addressee,
> please inform the sender immediately.
>
> This message is confidential and may not be redistributed or
> broadcast in whole or part in any form, including but not limited
> to any form of internet transmission including email, usenet,
> newsgroups, www, irc, icq, etc.
> All liability for errors and viruses is disclaimed.
RE: [DISCUSS] next release / roadmap
Posted by Zack Shoylev <za...@RACKSPACE.COM>.
Quick update, I have now fixed the compute live test problems for cloudfiles-us.
________________________________________
From: Zack Shoylev [zack.shoylev@RACKSPACE.COM]
Sent: Wednesday, January 28, 2015 11:13 AM
To: dev@jclouds.apache.org
Subject: RE: [DISCUSS] next release / roadmap
Some good news, blobstore and compute for rackspace now are live-tested (thanks Everett) here:
https://jclouds.ci.cloudbees.com/view/live%20tests/
Compute has 4 failures from what I see. Should be possible to figure those out for next release.
>From what I remember those are image OS related (such as OS version mismatch).
Thanks!
________________________________________
From: Andrew Phillips [aphillips@qrmedia.com]
Sent: Tuesday, January 27, 2015 8:28 AM
To: dev@jclouds.apache.org
Subject: Re: [DISCUSS] next release / roadmap
> There are failures in AWS compute (I'll volunteer to take a look at
> them), in the blobstore providers you mentioned, and there are also
> many failures in rackspace compute, that I've been reporting for
> several releases. Those failures should be addressed too in this
> release.
As a first step, do we know whether we have issues in JIRA (with the
correct fix version etc.) for all these issues? Then we can hopefully
use JIRA as a "proper" backlog management tool for 1.9.0.
Thanks for the JIRA cleanup work, Andrew G and Jeremy!
Regards
ap
--
Andrew Phillips
qrmedia
Unless expressly stated otherwise, this message is confidential.
Access to this e-mail by anyone else is unauthorised. If you are
not an addressee, any disclosure or copying of the contents of
this e-mail or any action taken (or not taken) in reliance on it
is unauthorised and may be unlawful. If you are not an addressee,
please inform the sender immediately.
This message is confidential and may not be redistributed or
broadcast in whole or part in any form, including but not limited
to any form of internet transmission including email, usenet,
newsgroups, www, irc, icq, etc.
All liability for errors and viruses is disclaimed.
RE: [DISCUSS] next release / roadmap
Posted by Zack Shoylev <za...@RACKSPACE.COM>.
Some good news, blobstore and compute for rackspace now are live-tested (thanks Everett) here:
https://jclouds.ci.cloudbees.com/view/live%20tests/
Compute has 4 failures from what I see. Should be possible to figure those out for next release.
>From what I remember those are image OS related (such as OS version mismatch).
Thanks!
________________________________________
From: Andrew Phillips [aphillips@qrmedia.com]
Sent: Tuesday, January 27, 2015 8:28 AM
To: dev@jclouds.apache.org
Subject: Re: [DISCUSS] next release / roadmap
> There are failures in AWS compute (I'll volunteer to take a look at
> them), in the blobstore providers you mentioned, and there are also
> many failures in rackspace compute, that I've been reporting for
> several releases. Those failures should be addressed too in this
> release.
As a first step, do we know whether we have issues in JIRA (with the
correct fix version etc.) for all these issues? Then we can hopefully
use JIRA as a "proper" backlog management tool for 1.9.0.
Thanks for the JIRA cleanup work, Andrew G and Jeremy!
Regards
ap
--
Andrew Phillips
qrmedia
Unless expressly stated otherwise, this message is confidential.
Access to this e-mail by anyone else is unauthorised. If you are
not an addressee, any disclosure or copying of the contents of
this e-mail or any action taken (or not taken) in reliance on it
is unauthorised and may be unlawful. If you are not an addressee,
please inform the sender immediately.
This message is confidential and may not be redistributed or
broadcast in whole or part in any form, including but not limited
to any form of internet transmission including email, usenet,
newsgroups, www, irc, icq, etc.
All liability for errors and viruses is disclaimed.
Re: [DISCUSS] next release / roadmap
Posted by Andrew Phillips <ap...@qrmedia.com>.
> There are failures in AWS compute (I'll volunteer to take a look at
> them), in the blobstore providers you mentioned, and there are also
> many failures in rackspace compute, that I've been reporting for
> several releases. Those failures should be addressed too in this
> release.
As a first step, do we know whether we have issues in JIRA (with the
correct fix version etc.) for all these issues? Then we can hopefully
use JIRA as a "proper" backlog management tool for 1.9.0.
Thanks for the JIRA cleanup work, Andrew G and Jeremy!
Regards
ap
--
Andrew Phillips
qrmedia
Unless expressly stated otherwise, this message is confidential.
Access to this e-mail by anyone else is unauthorised. If you are
not an addressee, any disclosure or copying of the contents of
this e-mail or any action taken (or not taken) in reliance on it
is unauthorised and may be unlawful. If you are not an addressee,
please inform the sender immediately.
This message is confidential and may not be redistributed or
broadcast in whole or part in any form, including but not limited
to any form of internet transmission including email, usenet,
newsgroups, www, irc, icq, etc.
All liability for errors and viruses is disclaimed.
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <ig...@gmail.com>.
I also want to move forward with the release, but I'd like to make
sure we fix our broken windows in it.
I agree with you Andrew G. that those tasks can be deferred, but I
really think it is important to address the live test failures in this
one.
There are failures in AWS compute (I'll volunteer to take a look at
them), in the blobstore providers you mentioned, and there are also
many failures in rackspace compute, that I've been reporting for
several releases. Those failures should be addressed too in this
release. If we want to say we support all major providers in the next
release, we should fix the ones we already have in this one so we can
focus on what we're missing for the next release.
On 22 January 2015 at 20:02, Andrew Gaul <ga...@apache.org> wrote:
> On Thu, Jan 22, 2015 at 10:34:54AM +0000, Andrea Turli wrote:
>> quick update on the must-have list:
>>
>> * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
>
> I will take look at the aws-s3 live test failures this weekend. We also
> have reports for failures against google-cloud-storage[JCLOUDS-805] and
> rackspace-cloudfiles-us[JCLOUDS-800]. Bhathiya is looking into the
> former; can someone from Rackspace investigate the latter?
>
>> * Remove the old Swift provider.
>
> We should not remove this api or its providers in 1.9.0 since its
> replacement does not have feature parity, specifically multi-part upload
> support[JCLOUDS-760]. However, if we could add providers for hpcloud
> and softlayer this would allow many users to migrate.
>
>> * Support AWS signature version 4. (JCLOUDS-480 [3])
>> * Promote the OAuth API. It is now used only by GCE but if I'm not
>> wrong it will be used by the DigitalOcean v2 api too.
>> * Promote Google Compute Engine.
>> - Fix all failing live tests (there are not many).
>> - Remove its SecurityGroupExtension, as the current implementation
>> and how firewalls work in GCE is not aligned with how the SGE works.
>> * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
>> * Study the uses of the Apache HttpClient driver and consider
>> migrating to the OkHttp one. The output of this task should be a plan
>> to upgrade or remove the Apache HC driver.
>
> None of these seem like release blockers; can we defer them to 2.0.0?
>
>> * Support Docker 1.3.2 (Complete the corresponding PR [4]) -> closed
>>
>> For what I can see only Docker support has been closed.
>>
>> Do we have any update on the others? I'd really like to move faster to
>> 1.9.0-rc release at least, so I'll be happy to help with any of them.
>
> I would also like to move forward with a release; master has almost six
> months worth of features since the last major release and three months
> worth of bug fixes since the last minor release. Can we identify any
> blocking issues with fixVersion = 1.9.0 in JIRA:
>
> https://issues.apache.org/jira/browse/JCLOUDS-791?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.9.0
>
> I will add a few other potential blockers.
>
> --
> Andrew Gaul
> http://gaul.org/
Re: [DISCUSS] next release / roadmap
Posted by Andrew Gaul <ga...@apache.org>.
On Thu, Jan 22, 2015 at 10:34:54AM +0000, Andrea Turli wrote:
> quick update on the must-have list:
>
> * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
I will take look at the aws-s3 live test failures this weekend. We also
have reports for failures against google-cloud-storage[JCLOUDS-805] and
rackspace-cloudfiles-us[JCLOUDS-800]. Bhathiya is looking into the
former; can someone from Rackspace investigate the latter?
> * Remove the old Swift provider.
We should not remove this api or its providers in 1.9.0 since its
replacement does not have feature parity, specifically multi-part upload
support[JCLOUDS-760]. However, if we could add providers for hpcloud
and softlayer this would allow many users to migrate.
> * Support AWS signature version 4. (JCLOUDS-480 [3])
> * Promote the OAuth API. It is now used only by GCE but if I'm not
> wrong it will be used by the DigitalOcean v2 api too.
> * Promote Google Compute Engine.
> - Fix all failing live tests (there are not many).
> - Remove its SecurityGroupExtension, as the current implementation
> and how firewalls work in GCE is not aligned with how the SGE works.
> * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
> * Study the uses of the Apache HttpClient driver and consider
> migrating to the OkHttp one. The output of this task should be a plan
> to upgrade or remove the Apache HC driver.
None of these seem like release blockers; can we defer them to 2.0.0?
> * Support Docker 1.3.2 (Complete the corresponding PR [4]) -> closed
>
> For what I can see only Docker support has been closed.
>
> Do we have any update on the others? I'd really like to move faster to
> 1.9.0-rc release at least, so I'll be happy to help with any of them.
I would also like to move forward with a release; master has almost six
months worth of features since the last major release and three months
worth of bug fixes since the last minor release. Can we identify any
blocking issues with fixVersion = 1.9.0 in JIRA:
https://issues.apache.org/jira/browse/JCLOUDS-791?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.9.0
I will add a few other potential blockers.
--
Andrew Gaul
http://gaul.org/
Re: [DISCUSS] next release / roadmap
Posted by Andrea Turli <an...@gmail.com>.
Hi there,
quick update on the must-have list:
* Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
* Support AWS signature version 4. (JCLOUDS-480 [3])
* Remove the old Swift provider.
* Promote the OAuth API. It is now used only by GCE but if I'm not
wrong it will be used by the DigitalOcean v2 api too.
* Promote Google Compute Engine.
- Fix all failing live tests (there are not many).
- Remove its SecurityGroupExtension, as the current implementation
and how firewalls work in GCE is not aligned with how the SGE works.
* Support Docker 1.3.2 (Complete the corresponding PR [4]) -> closed
* Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
* Study the uses of the Apache HttpClient driver and consider
migrating to the OkHttp one. The output of this task should be a plan
to upgrade or remove the Apache HC driver.
For what I can see only Docker support has been closed.
Do we have any update on the others? I'd really like to move faster to
1.9.0-rc release at least, so I'll be happy to help with any of them.
Best,
Andrea
[1] https://issues.apache.org/jira/browse/JCLOUDS-462
[2] https://issues.apache.org/jira/browse/JCLOUDS-775
[3] https://issues.apache.org/jira/browse/JCLOUDS-480
[4] https://github.com/jclouds/jclouds-labs/pull/113
[5] https://issues.apache.org/jira/browse/JCLOUDS-104
On Thu Jan 15 2015 at 4:23:26 PM Ignasi Barrera <ig...@gmail.com>
wrote:
> I don't think so. Everything that is under development now should be
> part of the next release, so I'd keep master as the next release
> branch. Once released we can take 1.9.x out, as we always do.
> Is there any intention to merge something to master that should *not*
> be part of the next release?
>
> On 15 January 2015 at 16:03, Andrea Turli <an...@gmail.com> wrote:
> > As next release will be 1.9.0, could we now create new branches 1.9.x out
> > of current masters?
> >
> > On Tue Jan 13 2015 at 5:17:20 PM Ignasi Barrera <na...@apache.org> wrote:
> >
> >> Regarding the TODOs, Dan has done a great job in GCE and I helped with
> >> the live tests. Most of them are passing now, if not all, so having
> >> OAuth and GCE promoted by the end of January should be possible (I've
> >> already removed the SecurityGroupExtension from GCE).
> >>
> >> Apart from that, there are still things TBD that IMO (as I said in my
> >> previous email) are a must for the next release.
> >> To me, being able to release by the end of January/beginning of
> >> February depends entirely on that TODO list being completed.
> >>
> >> On 13 January 2015 at 00:24, Zack Shoylev <za...@rackspace.com>
> >> wrote:
> >> > Is end of January/beginning of February a good target timeframe for
> 1.9?
> >> > Any other big items left?
> >> > ________________________________________
> >> > From: Chris Custine [chris.custine@gmail.com]
> >> > Sent: Friday, December 12, 2014 3:24 PM
> >> > To: dev@jclouds.apache.org; Ignasi Barrera
> >> > Subject: Re: [DISCUSS] next release / roadmap
> >> >
> >> > I agree 100% with Ignasi that the next release should be 1.9 as
> >> discussed a few months ago.
> >> >
> >> > I am putting myself on the hook for the following tasks before 1.9 or
> >> whatever the next release is called:
> >> > - Upgrade the HP Object Storage provider to the new Swift API
> provider,
> >> which has been a blocker for finally removing the old swift provider.
> >> > - Finalizing the Digital Ocean v2 API provider for labs (which would
> >> benefit from the OAuth promotion as Ignasi mentioned)
> >> > - Review of any GCE PRs/fixes and migration
> >> >
> >> > There is definitely a lot of work to be done, in addition to the
> >> inevitable holiday time suck, so I can’t see us doing a release by end
> of
> >> year. My personal experience is that early January brings inspiration
> and
> >> more plentiful energy to make progress on these things, but we certainly
> >> can move forward at our best pace in the mean time.
> >> >
> >> > Thanks,
> >> > Chris
> >> > --
> >> > Chris Custine
> >> >
> >> >
> >> > From: Ignasi Barrera <na...@apache.org>
> >> > Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
> >> > Date: December 10, 2014 at 2:30:42 PM
> >> > To: dev@jclouds.apache.org <de...@jclouds.apache.org>>
> >> > Subject: Re: [DISCUSS] next release / roadmap
> >> >
> >> > In my opinion, the next release should be a 1.9.0, containing the
> >> > changes that "prepare" jclouds for the next major release. It is a
> >> > "fix our broken windows" release, as it will ship the complete
> >> > de-async stuff, it will remove several obsolete providers, and it will
> >> > promote others.
> >> >
> >> > This is the must-have list (in my opinion) for 1.9.0:
> >> >
> >> > * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
> >> > * Support AWS signature version 4. (JCLOUDS-480 [3])
> >> > * Remove the old Swift provider.
> >> > * Promote the OAuth API. It is now used only by GCE but if I'm not
> >> > wrong it will be used by the DigitalOcean v2 api too.
> >> > * Promote Google Compute Engine.
> >> > - Fix all failing live tests (there are not many).
> >> > - Remove its SecurityGroupExtension, as the current implementation
> >> > and how firewalls work in GCE is not aligned with how the SGE works.
> >> > * Support Docker 1.3.2 (Complete the corresponding PR [4])
> >> > * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104
> [5])
> >> > * Study the uses of the Apache HttpClient driver and consider
> >> > migrating to the OkHttp one. The output of this task should be a plan
> >> > to upgrade or remove the Apache HC driver.
> >> >
> >> > In that release, we should make sure that all live tests pass for the
> >> > major providers:
> >> >
> >> > * AWS
> >> > * Rackspace
> >> > * Google
> >> > * Azureblob (and ideally compute, despite being in labs)
> >> >
> >> >
> >> > Regarding the timing, I think we are not yet in a good position to set
> >> > a hard (or even soft) date. We'd better first come up with the TODO
> >> > list, and hopefully distribute the work so we can all work together to
> >> > make that release happen, even if that means getting out of our
> >> > comfort area (or comfort providers).
> >> >
> >> > Ignasi
> >> >
> >> >
> >> > [1] https://issues.apache.org/jira/browse/JCLOUDS-462
> >> > [2] https://issues.apache.org/jira/browse/JCLOUDS-775
> >> > [3] https://issues.apache.org/jira/browse/JCLOUDS-480
> >> > [4] https://github.com/jclouds/jclouds-labs/pull/113
> >> > [5] https://issues.apache.org/jira/browse/JCLOUDS-104
> >> >
> >> >
> >> >
> >> > On 8 December 2014 at 21:05, Zack Shoylev <zack.shoylev@rackspace.com
> >
> >> wrote:
> >> >> I wanted to start a discussion about getting the next release done.
> >> Here are some questions that we should discuss. Feel free to add more
> (what
> >> am I missing here?). This will also help us get on the same page.
> >> >>
> >> >> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
> >> >>
> >> >> 2. What should be the minimum included in it?
> >> >>
> >> >> 3. Can we get a release out by the end of December (considering
> >> holidays)?
> >> >>
> >> >> Thanks,
> >> >> Zack
> >>
>
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <ig...@gmail.com>.
I don't think so. Everything that is under development now should be
part of the next release, so I'd keep master as the next release
branch. Once released we can take 1.9.x out, as we always do.
Is there any intention to merge something to master that should *not*
be part of the next release?
On 15 January 2015 at 16:03, Andrea Turli <an...@gmail.com> wrote:
> As next release will be 1.9.0, could we now create new branches 1.9.x out
> of current masters?
>
> On Tue Jan 13 2015 at 5:17:20 PM Ignasi Barrera <na...@apache.org> wrote:
>
>> Regarding the TODOs, Dan has done a great job in GCE and I helped with
>> the live tests. Most of them are passing now, if not all, so having
>> OAuth and GCE promoted by the end of January should be possible (I've
>> already removed the SecurityGroupExtension from GCE).
>>
>> Apart from that, there are still things TBD that IMO (as I said in my
>> previous email) are a must for the next release.
>> To me, being able to release by the end of January/beginning of
>> February depends entirely on that TODO list being completed.
>>
>> On 13 January 2015 at 00:24, Zack Shoylev <za...@rackspace.com>
>> wrote:
>> > Is end of January/beginning of February a good target timeframe for 1.9?
>> > Any other big items left?
>> > ________________________________________
>> > From: Chris Custine [chris.custine@gmail.com]
>> > Sent: Friday, December 12, 2014 3:24 PM
>> > To: dev@jclouds.apache.org; Ignasi Barrera
>> > Subject: Re: [DISCUSS] next release / roadmap
>> >
>> > I agree 100% with Ignasi that the next release should be 1.9 as
>> discussed a few months ago.
>> >
>> > I am putting myself on the hook for the following tasks before 1.9 or
>> whatever the next release is called:
>> > - Upgrade the HP Object Storage provider to the new Swift API provider,
>> which has been a blocker for finally removing the old swift provider.
>> > - Finalizing the Digital Ocean v2 API provider for labs (which would
>> benefit from the OAuth promotion as Ignasi mentioned)
>> > - Review of any GCE PRs/fixes and migration
>> >
>> > There is definitely a lot of work to be done, in addition to the
>> inevitable holiday time suck, so I can’t see us doing a release by end of
>> year. My personal experience is that early January brings inspiration and
>> more plentiful energy to make progress on these things, but we certainly
>> can move forward at our best pace in the mean time.
>> >
>> > Thanks,
>> > Chris
>> > --
>> > Chris Custine
>> >
>> >
>> > From: Ignasi Barrera <na...@apache.org>
>> > Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
>> > Date: December 10, 2014 at 2:30:42 PM
>> > To: dev@jclouds.apache.org <de...@jclouds.apache.org>>
>> > Subject: Re: [DISCUSS] next release / roadmap
>> >
>> > In my opinion, the next release should be a 1.9.0, containing the
>> > changes that "prepare" jclouds for the next major release. It is a
>> > "fix our broken windows" release, as it will ship the complete
>> > de-async stuff, it will remove several obsolete providers, and it will
>> > promote others.
>> >
>> > This is the must-have list (in my opinion) for 1.9.0:
>> >
>> > * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
>> > * Support AWS signature version 4. (JCLOUDS-480 [3])
>> > * Remove the old Swift provider.
>> > * Promote the OAuth API. It is now used only by GCE but if I'm not
>> > wrong it will be used by the DigitalOcean v2 api too.
>> > * Promote Google Compute Engine.
>> > - Fix all failing live tests (there are not many).
>> > - Remove its SecurityGroupExtension, as the current implementation
>> > and how firewalls work in GCE is not aligned with how the SGE works.
>> > * Support Docker 1.3.2 (Complete the corresponding PR [4])
>> > * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
>> > * Study the uses of the Apache HttpClient driver and consider
>> > migrating to the OkHttp one. The output of this task should be a plan
>> > to upgrade or remove the Apache HC driver.
>> >
>> > In that release, we should make sure that all live tests pass for the
>> > major providers:
>> >
>> > * AWS
>> > * Rackspace
>> > * Google
>> > * Azureblob (and ideally compute, despite being in labs)
>> >
>> >
>> > Regarding the timing, I think we are not yet in a good position to set
>> > a hard (or even soft) date. We'd better first come up with the TODO
>> > list, and hopefully distribute the work so we can all work together to
>> > make that release happen, even if that means getting out of our
>> > comfort area (or comfort providers).
>> >
>> > Ignasi
>> >
>> >
>> > [1] https://issues.apache.org/jira/browse/JCLOUDS-462
>> > [2] https://issues.apache.org/jira/browse/JCLOUDS-775
>> > [3] https://issues.apache.org/jira/browse/JCLOUDS-480
>> > [4] https://github.com/jclouds/jclouds-labs/pull/113
>> > [5] https://issues.apache.org/jira/browse/JCLOUDS-104
>> >
>> >
>> >
>> > On 8 December 2014 at 21:05, Zack Shoylev <za...@rackspace.com>
>> wrote:
>> >> I wanted to start a discussion about getting the next release done.
>> Here are some questions that we should discuss. Feel free to add more (what
>> am I missing here?). This will also help us get on the same page.
>> >>
>> >> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
>> >>
>> >> 2. What should be the minimum included in it?
>> >>
>> >> 3. Can we get a release out by the end of December (considering
>> holidays)?
>> >>
>> >> Thanks,
>> >> Zack
>>
Re: [DISCUSS] next release / roadmap
Posted by Andrea Turli <an...@gmail.com>.
As next release will be 1.9.0, could we now create new branches 1.9.x out
of current masters?
On Tue Jan 13 2015 at 5:17:20 PM Ignasi Barrera <na...@apache.org> wrote:
> Regarding the TODOs, Dan has done a great job in GCE and I helped with
> the live tests. Most of them are passing now, if not all, so having
> OAuth and GCE promoted by the end of January should be possible (I've
> already removed the SecurityGroupExtension from GCE).
>
> Apart from that, there are still things TBD that IMO (as I said in my
> previous email) are a must for the next release.
> To me, being able to release by the end of January/beginning of
> February depends entirely on that TODO list being completed.
>
> On 13 January 2015 at 00:24, Zack Shoylev <za...@rackspace.com>
> wrote:
> > Is end of January/beginning of February a good target timeframe for 1.9?
> > Any other big items left?
> > ________________________________________
> > From: Chris Custine [chris.custine@gmail.com]
> > Sent: Friday, December 12, 2014 3:24 PM
> > To: dev@jclouds.apache.org; Ignasi Barrera
> > Subject: Re: [DISCUSS] next release / roadmap
> >
> > I agree 100% with Ignasi that the next release should be 1.9 as
> discussed a few months ago.
> >
> > I am putting myself on the hook for the following tasks before 1.9 or
> whatever the next release is called:
> > - Upgrade the HP Object Storage provider to the new Swift API provider,
> which has been a blocker for finally removing the old swift provider.
> > - Finalizing the Digital Ocean v2 API provider for labs (which would
> benefit from the OAuth promotion as Ignasi mentioned)
> > - Review of any GCE PRs/fixes and migration
> >
> > There is definitely a lot of work to be done, in addition to the
> inevitable holiday time suck, so I can’t see us doing a release by end of
> year. My personal experience is that early January brings inspiration and
> more plentiful energy to make progress on these things, but we certainly
> can move forward at our best pace in the mean time.
> >
> > Thanks,
> > Chris
> > --
> > Chris Custine
> >
> >
> > From: Ignasi Barrera <na...@apache.org>
> > Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
> > Date: December 10, 2014 at 2:30:42 PM
> > To: dev@jclouds.apache.org <de...@jclouds.apache.org>>
> > Subject: Re: [DISCUSS] next release / roadmap
> >
> > In my opinion, the next release should be a 1.9.0, containing the
> > changes that "prepare" jclouds for the next major release. It is a
> > "fix our broken windows" release, as it will ship the complete
> > de-async stuff, it will remove several obsolete providers, and it will
> > promote others.
> >
> > This is the must-have list (in my opinion) for 1.9.0:
> >
> > * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
> > * Support AWS signature version 4. (JCLOUDS-480 [3])
> > * Remove the old Swift provider.
> > * Promote the OAuth API. It is now used only by GCE but if I'm not
> > wrong it will be used by the DigitalOcean v2 api too.
> > * Promote Google Compute Engine.
> > - Fix all failing live tests (there are not many).
> > - Remove its SecurityGroupExtension, as the current implementation
> > and how firewalls work in GCE is not aligned with how the SGE works.
> > * Support Docker 1.3.2 (Complete the corresponding PR [4])
> > * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
> > * Study the uses of the Apache HttpClient driver and consider
> > migrating to the OkHttp one. The output of this task should be a plan
> > to upgrade or remove the Apache HC driver.
> >
> > In that release, we should make sure that all live tests pass for the
> > major providers:
> >
> > * AWS
> > * Rackspace
> > * Google
> > * Azureblob (and ideally compute, despite being in labs)
> >
> >
> > Regarding the timing, I think we are not yet in a good position to set
> > a hard (or even soft) date. We'd better first come up with the TODO
> > list, and hopefully distribute the work so we can all work together to
> > make that release happen, even if that means getting out of our
> > comfort area (or comfort providers).
> >
> > Ignasi
> >
> >
> > [1] https://issues.apache.org/jira/browse/JCLOUDS-462
> > [2] https://issues.apache.org/jira/browse/JCLOUDS-775
> > [3] https://issues.apache.org/jira/browse/JCLOUDS-480
> > [4] https://github.com/jclouds/jclouds-labs/pull/113
> > [5] https://issues.apache.org/jira/browse/JCLOUDS-104
> >
> >
> >
> > On 8 December 2014 at 21:05, Zack Shoylev <za...@rackspace.com>
> wrote:
> >> I wanted to start a discussion about getting the next release done.
> Here are some questions that we should discuss. Feel free to add more (what
> am I missing here?). This will also help us get on the same page.
> >>
> >> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
> >>
> >> 2. What should be the minimum included in it?
> >>
> >> 3. Can we get a release out by the end of December (considering
> holidays)?
> >>
> >> Thanks,
> >> Zack
>
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <na...@apache.org>.
Regarding the TODOs, Dan has done a great job in GCE and I helped with
the live tests. Most of them are passing now, if not all, so having
OAuth and GCE promoted by the end of January should be possible (I've
already removed the SecurityGroupExtension from GCE).
Apart from that, there are still things TBD that IMO (as I said in my
previous email) are a must for the next release.
To me, being able to release by the end of January/beginning of
February depends entirely on that TODO list being completed.
On 13 January 2015 at 00:24, Zack Shoylev <za...@rackspace.com> wrote:
> Is end of January/beginning of February a good target timeframe for 1.9?
> Any other big items left?
> ________________________________________
> From: Chris Custine [chris.custine@gmail.com]
> Sent: Friday, December 12, 2014 3:24 PM
> To: dev@jclouds.apache.org; Ignasi Barrera
> Subject: Re: [DISCUSS] next release / roadmap
>
> I agree 100% with Ignasi that the next release should be 1.9 as discussed a few months ago.
>
> I am putting myself on the hook for the following tasks before 1.9 or whatever the next release is called:
> - Upgrade the HP Object Storage provider to the new Swift API provider, which has been a blocker for finally removing the old swift provider.
> - Finalizing the Digital Ocean v2 API provider for labs (which would benefit from the OAuth promotion as Ignasi mentioned)
> - Review of any GCE PRs/fixes and migration
>
> There is definitely a lot of work to be done, in addition to the inevitable holiday time suck, so I can’t see us doing a release by end of year. My personal experience is that early January brings inspiration and more plentiful energy to make progress on these things, but we certainly can move forward at our best pace in the mean time.
>
> Thanks,
> Chris
> --
> Chris Custine
>
>
> From: Ignasi Barrera <na...@apache.org>
> Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
> Date: December 10, 2014 at 2:30:42 PM
> To: dev@jclouds.apache.org <de...@jclouds.apache.org>>
> Subject: Re: [DISCUSS] next release / roadmap
>
> In my opinion, the next release should be a 1.9.0, containing the
> changes that "prepare" jclouds for the next major release. It is a
> "fix our broken windows" release, as it will ship the complete
> de-async stuff, it will remove several obsolete providers, and it will
> promote others.
>
> This is the must-have list (in my opinion) for 1.9.0:
>
> * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
> * Support AWS signature version 4. (JCLOUDS-480 [3])
> * Remove the old Swift provider.
> * Promote the OAuth API. It is now used only by GCE but if I'm not
> wrong it will be used by the DigitalOcean v2 api too.
> * Promote Google Compute Engine.
> - Fix all failing live tests (there are not many).
> - Remove its SecurityGroupExtension, as the current implementation
> and how firewalls work in GCE is not aligned with how the SGE works.
> * Support Docker 1.3.2 (Complete the corresponding PR [4])
> * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
> * Study the uses of the Apache HttpClient driver and consider
> migrating to the OkHttp one. The output of this task should be a plan
> to upgrade or remove the Apache HC driver.
>
> In that release, we should make sure that all live tests pass for the
> major providers:
>
> * AWS
> * Rackspace
> * Google
> * Azureblob (and ideally compute, despite being in labs)
>
>
> Regarding the timing, I think we are not yet in a good position to set
> a hard (or even soft) date. We'd better first come up with the TODO
> list, and hopefully distribute the work so we can all work together to
> make that release happen, even if that means getting out of our
> comfort area (or comfort providers).
>
> Ignasi
>
>
> [1] https://issues.apache.org/jira/browse/JCLOUDS-462
> [2] https://issues.apache.org/jira/browse/JCLOUDS-775
> [3] https://issues.apache.org/jira/browse/JCLOUDS-480
> [4] https://github.com/jclouds/jclouds-labs/pull/113
> [5] https://issues.apache.org/jira/browse/JCLOUDS-104
>
>
>
> On 8 December 2014 at 21:05, Zack Shoylev <za...@rackspace.com> wrote:
>> I wanted to start a discussion about getting the next release done. Here are some questions that we should discuss. Feel free to add more (what am I missing here?). This will also help us get on the same page.
>>
>> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
>>
>> 2. What should be the minimum included in it?
>>
>> 3. Can we get a release out by the end of December (considering holidays)?
>>
>> Thanks,
>> Zack
RE: [DISCUSS] next release / roadmap
Posted by Zack Shoylev <za...@RACKSPACE.COM>.
Is end of January/beginning of February a good target timeframe for 1.9?
Any other big items left?
________________________________________
From: Chris Custine [chris.custine@gmail.com]
Sent: Friday, December 12, 2014 3:24 PM
To: dev@jclouds.apache.org; Ignasi Barrera
Subject: Re: [DISCUSS] next release / roadmap
I agree 100% with Ignasi that the next release should be 1.9 as discussed a few months ago.
I am putting myself on the hook for the following tasks before 1.9 or whatever the next release is called:
- Upgrade the HP Object Storage provider to the new Swift API provider, which has been a blocker for finally removing the old swift provider.
- Finalizing the Digital Ocean v2 API provider for labs (which would benefit from the OAuth promotion as Ignasi mentioned)
- Review of any GCE PRs/fixes and migration
There is definitely a lot of work to be done, in addition to the inevitable holiday time suck, so I can’t see us doing a release by end of year. My personal experience is that early January brings inspiration and more plentiful energy to make progress on these things, but we certainly can move forward at our best pace in the mean time.
Thanks,
Chris
--
Chris Custine
From: Ignasi Barrera <na...@apache.org>
Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
Date: December 10, 2014 at 2:30:42 PM
To: dev@jclouds.apache.org <de...@jclouds.apache.org>>
Subject: Re: [DISCUSS] next release / roadmap
In my opinion, the next release should be a 1.9.0, containing the
changes that "prepare" jclouds for the next major release. It is a
"fix our broken windows" release, as it will ship the complete
de-async stuff, it will remove several obsolete providers, and it will
promote others.
This is the must-have list (in my opinion) for 1.9.0:
* Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
* Support AWS signature version 4. (JCLOUDS-480 [3])
* Remove the old Swift provider.
* Promote the OAuth API. It is now used only by GCE but if I'm not
wrong it will be used by the DigitalOcean v2 api too.
* Promote Google Compute Engine.
- Fix all failing live tests (there are not many).
- Remove its SecurityGroupExtension, as the current implementation
and how firewalls work in GCE is not aligned with how the SGE works.
* Support Docker 1.3.2 (Complete the corresponding PR [4])
* Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
* Study the uses of the Apache HttpClient driver and consider
migrating to the OkHttp one. The output of this task should be a plan
to upgrade or remove the Apache HC driver.
In that release, we should make sure that all live tests pass for the
major providers:
* AWS
* Rackspace
* Google
* Azureblob (and ideally compute, despite being in labs)
Regarding the timing, I think we are not yet in a good position to set
a hard (or even soft) date. We'd better first come up with the TODO
list, and hopefully distribute the work so we can all work together to
make that release happen, even if that means getting out of our
comfort area (or comfort providers).
Ignasi
[1] https://issues.apache.org/jira/browse/JCLOUDS-462
[2] https://issues.apache.org/jira/browse/JCLOUDS-775
[3] https://issues.apache.org/jira/browse/JCLOUDS-480
[4] https://github.com/jclouds/jclouds-labs/pull/113
[5] https://issues.apache.org/jira/browse/JCLOUDS-104
On 8 December 2014 at 21:05, Zack Shoylev <za...@rackspace.com> wrote:
> I wanted to start a discussion about getting the next release done. Here are some questions that we should discuss. Feel free to add more (what am I missing here?). This will also help us get on the same page.
>
> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
>
> 2. What should be the minimum included in it?
>
> 3. Can we get a release out by the end of December (considering holidays)?
>
> Thanks,
> Zack
Re: [DISCUSS] next release / roadmap
Posted by Chris Custine <ch...@gmail.com>.
I agree 100% with Ignasi that the next release should be 1.9 as discussed a few months ago.
I am putting myself on the hook for the following tasks before 1.9 or whatever the next release is called:
- Upgrade the HP Object Storage provider to the new Swift API provider, which has been a blocker for finally removing the old swift provider.
- Finalizing the Digital Ocean v2 API provider for labs (which would benefit from the OAuth promotion as Ignasi mentioned)
- Review of any GCE PRs/fixes and migration
There is definitely a lot of work to be done, in addition to the inevitable holiday time suck, so I can’t see us doing a release by end of year. My personal experience is that early January brings inspiration and more plentiful energy to make progress on these things, but we certainly can move forward at our best pace in the mean time.
Thanks,
Chris
--
Chris Custine
From: Ignasi Barrera <na...@apache.org>
Reply: dev@jclouds.apache.org <de...@jclouds.apache.org>>
Date: December 10, 2014 at 2:30:42 PM
To: dev@jclouds.apache.org <de...@jclouds.apache.org>>
Subject: Re: [DISCUSS] next release / roadmap
In my opinion, the next release should be a 1.9.0, containing the
changes that "prepare" jclouds for the next major release. It is a
"fix our broken windows" release, as it will ship the complete
de-async stuff, it will remove several obsolete providers, and it will
promote others.
This is the must-have list (in my opinion) for 1.9.0:
* Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
* Support AWS signature version 4. (JCLOUDS-480 [3])
* Remove the old Swift provider.
* Promote the OAuth API. It is now used only by GCE but if I'm not
wrong it will be used by the DigitalOcean v2 api too.
* Promote Google Compute Engine.
- Fix all failing live tests (there are not many).
- Remove its SecurityGroupExtension, as the current implementation
and how firewalls work in GCE is not aligned with how the SGE works.
* Support Docker 1.3.2 (Complete the corresponding PR [4])
* Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
* Study the uses of the Apache HttpClient driver and consider
migrating to the OkHttp one. The output of this task should be a plan
to upgrade or remove the Apache HC driver.
In that release, we should make sure that all live tests pass for the
major providers:
* AWS
* Rackspace
* Google
* Azureblob (and ideally compute, despite being in labs)
Regarding the timing, I think we are not yet in a good position to set
a hard (or even soft) date. We'd better first come up with the TODO
list, and hopefully distribute the work so we can all work together to
make that release happen, even if that means getting out of our
comfort area (or comfort providers).
Ignasi
[1] https://issues.apache.org/jira/browse/JCLOUDS-462
[2] https://issues.apache.org/jira/browse/JCLOUDS-775
[3] https://issues.apache.org/jira/browse/JCLOUDS-480
[4] https://github.com/jclouds/jclouds-labs/pull/113
[5] https://issues.apache.org/jira/browse/JCLOUDS-104
On 8 December 2014 at 21:05, Zack Shoylev <za...@rackspace.com> wrote:
> I wanted to start a discussion about getting the next release done. Here are some questions that we should discuss. Feel free to add more (what am I missing here?). This will also help us get on the same page.
>
> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
>
> 2. What should be the minimum included in it?
>
> 3. Can we get a release out by the end of December (considering holidays)?
>
> Thanks,
> Zack
Re: [DISCUSS] next release / roadmap
Posted by Ignasi Barrera <na...@apache.org>.
In my opinion, the next release should be a 1.9.0, containing the
changes that "prepare" jclouds for the next major release. It is a
"fix our broken windows" release, as it will ship the complete
de-async stuff, it will remove several obsolete providers, and it will
promote others.
This is the must-have list (in my opinion) for 1.9.0:
* Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2])
* Support AWS signature version 4. (JCLOUDS-480 [3])
* Remove the old Swift provider.
* Promote the OAuth API. It is now used only by GCE but if I'm not
wrong it will be used by the DigitalOcean v2 api too.
* Promote Google Compute Engine.
- Fix all failing live tests (there are not many).
- Remove its SecurityGroupExtension, as the current implementation
and how firewalls work in GCE is not aligned with how the SGE works.
* Support Docker 1.3.2 (Complete the corresponding PR [4])
* Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5])
* Study the uses of the Apache HttpClient driver and consider
migrating to the OkHttp one. The output of this task should be a plan
to upgrade or remove the Apache HC driver.
In that release, we should make sure that all live tests pass for the
major providers:
* AWS
* Rackspace
* Google
* Azureblob (and ideally compute, despite being in labs)
Regarding the timing, I think we are not yet in a good position to set
a hard (or even soft) date. We'd better first come up with the TODO
list, and hopefully distribute the work so we can all work together to
make that release happen, even if that means getting out of our
comfort area (or comfort providers).
Ignasi
[1] https://issues.apache.org/jira/browse/JCLOUDS-462
[2] https://issues.apache.org/jira/browse/JCLOUDS-775
[3] https://issues.apache.org/jira/browse/JCLOUDS-480
[4] https://github.com/jclouds/jclouds-labs/pull/113
[5] https://issues.apache.org/jira/browse/JCLOUDS-104
On 8 December 2014 at 21:05, Zack Shoylev <za...@rackspace.com> wrote:
> I wanted to start a discussion about getting the next release done. Here are some questions that we should discuss. Feel free to add more (what am I missing here?). This will also help us get on the same page.
>
> 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ?
>
> 2. What should be the minimum included in it?
>
> 3. Can we get a release out by the end of December (considering holidays)?
>
> Thanks,
> Zack