We have several potential tasks for 1.8.0: 1) streamline release process 2) Guava 18 compatibility (JCLOUDS-622) 3) reparent chef to core
I suspect we need another week to finish these tasks; I can finish 2 but do we have owners for tasks 1 and 3? Given these outstanding tasks can we plan for either 21 or 28 July? I can help on either of these dates. On Fri, Jul 11, 2014 at 10:50:36PM +0000, Everett Toews wrote: > When do we want to begin the release of 1.8.0? > > My preference is always to start it on a Monday or Tuesday so we can get it > done by the end of the week but I’m open to whatever day. Let’s see how much > we can automate during this release. > > abayer, we’ll likely need you available at some point as you mentioned you > were able to get some automation done around the hellish entering of versions > as the release happens. > > 1. Week of July 14. > > I’m totally unavailable on the 14th but available the rest of the week. > > 2. Week of July 21. > > I’m at OSCON this week and totally unavailable to help. > > 3. Week of July 28. > > I’m free. > > > Thanks, > Everett > > > On Jul 1, 2014, at 12:00 PM, Everett Toews <everett.to...@rackspace.com> > wrote: > > > On Jun 30, 2014, at 7:34 PM, Shrinand Javadekar <shrin...@maginatics.com> > > wrote: > > > >> I was about to ask something similar. Is there a reason for having a > >> 1.7.4 and a 1.8.0 release? Can't we simply do a 1.8.0 to alleviate the > >> Guava pain and then do a v2.0 release? > > > > I should have parenthesized my proposal… > > > > ((1.7.4 xor 1.8.0) and then 2.0) > > > >> Also, IIRC one of the big ticket items in v2.0 was the graduation of > >> the new openstack implementation from jclouds-labs to the main jclouds > >> code. We should probably start that process sooner so that it gets as > >> much testing as possible (and possibly bug fixes). > > > > Agreed. We would only have 2 months to get openstack-swift into production > > ready shape. I think it’s possible but we need to start now. WDYT? > > > > Everett -- Andrew Gaul http://gaul.org/
