I forgot to add this to the list: * Fix the jclouds Karaf live tests [1]. It should not take more than one day, and it is a real must.
[1] https://issues.apache.org/jira/browse/JCLOUDS-1051 On 12 January 2016 at 00:12, Ignasi Barrera <n...@apache.org> wrote: > Hi John! > > Thanks for bringing this up. Planning a new release is a fantastic way > to start the new year! There have been several small discussions about > which should be the next release, and the consensus since 1.9.1 was to > not release another 1.9.x and focus on 2.0.0. It is going to be a > feature driven release instead of having a planned a hard date, and > this is the must-have list of pending tasks. I've tried to estimate > the amount of time required to complete them, to have a possible > release date: > > * Improve the compute image cache [1] (3 days). Patch is done [2] and > there is just one live test to fix. > * Add support for arbitrary CPU and RAM in the ComputeService [3] (1.5 weeks). > * Promote DigitalOcean v2 (1 hour). It is just moving code from one > repo to another [4], and it is a straightforward procedure. > * Promote Docker (1h) > * Promote ProfitBricks (3 days). There is a small live test to fix but > IMO we can promote the provider without it. See [5]. > * Promote Azure (1 week). There are several live test failures [6] > that have to be addressed before promoting the provider. > > With this planning in mind, I'm pretty confident that we can have > jclouds 2.0.0 released by the second week of February, as most of the > items are already advanced work in progress, and the others are > straightforward to implement. Anyway, feel free to discuss the list > and/or estimated timing. > > This said, releases should be community driven, so if this does not > work for you and there is a real community interest in having a 1.9.2 > released before, I'll be happy to make that happen. > > > Thanks for bringing this up! > > I. > > > [1] https://issues.apache.org/jira/browse/JCLOUDS-512 > [2] https://github.com/jclouds/jclouds/pull/885 > [3] https://issues.apache.org/jira/browse/JCLOUDS-482 > [4] > https://cwiki.apache.org/confluence/display/JCLOUDS/How+to+Promote+a+Provider > [5] https://github.com/jclouds/jclouds-labs/pull/224 > [6] https://github.com/jclouds/jclouds-labs/pull/197 > > > On 11 January 2016 at 21:11, John McDonnell <mcdonnell.j...@gmail.com> wrote: >> Hi Guys, >> >> Firstly thanks for providing this library! >> >> Im emailing in because I have 2 defects that I raised and resolved >> (JCLOUDS-991 & JCLOUDS-1021). According to Jira, they are both in the 1.9.X >> branch, but I guess they would be in next release, 1.9.2/2.0.0 >> >> Are their any plans for a 1.9.2 release soon? (I guess that 2.0.0 might be >> pushing it little..) As according to the confluence page[1] you release >> minor versions every 6 weeks, and the last 1.9.X was around August[2], so I >> guess there might be a minor release coming soon? >> >> I’d be interested in hearing about when this would be happening? >> >> I’d also consider helping out on the project in general. >> >> >> [1]: https://cwiki.apache.org/confluence/display/JCLOUDS/Release+Cadence >> <https://cwiki.apache.org/confluence/display/JCLOUDS/Release+Cadence> >> [2]: http://www.mail-archive.com/dev%40jclouds.apache.org/msg06157.html >> <http://www.mail-archive.com/dev@jclouds.apache.org/msg06157.html> >> >> Regards >> >> John
