+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 <andrea.tu...@gmail.com> Reply: dev@jclouds.apache.org <dev@jclouds.apache.org>> Date: March 11, 2015 at 2:26:18 AM To: dev@jclouds.apache.org <dev@jclouds.apache.org>>, Ignasi Barrera <n...@apache.org>> Subject: Re: [DISCUSS] next release / roadmap +1 Thanks Ignasi On Tue, Mar 10, 2015 at 11:11 PM Ignasi Barrera <n...@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 <n...@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 <g...@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 <n...@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 <n...@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.barr...@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.shoy...@rackspace.com> > >> > > wrote: > >> > > >>> Quick update, I have now fixed the compute live test problems > for > >> > > cloudfiles-us. > >> > > >>> ________________________________________ > >> > > >>> From: Zack Shoylev [zack.shoy...@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 [aphill...@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/ > > > > >
