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 <ignasi.barr...@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 <andrea.tu...@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 <n...@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 <zack.shoy...@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.cust...@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 <n...@apache.org> > >> > Reply: dev@jclouds.apache.org <dev@jclouds.apache.org>> > >> > Date: December 10, 2014 at 2:30:42 PM > >> > To: dev@jclouds.apache.org <dev@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.shoy...@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 > >> >
