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.
