Mike, I think this is important to do. For your plugin, you should branch off of storage_refactor and periodically pull from storage_refactor. That way we decouple to merge of the cloudstack hook-in work and the merge of your plugin.
Edison should be close to merging his work into master already so I don't want to keep piling things on to that branch and cause a delay in merge like what happened to javelin. --Alex > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Wednesday, February 06, 2013 9:43 PM > To: Marcus Sorensen > Cc: Mike Tutkowski; Devdeep Singh; cloudstack-dev@incubator.apache.org; > Edison Su > Subject: Re: storage_refactor branch > > On Wed, Feb 06, 2013 at 10:33:32PM -0700, Marcus Sorensen wrote: > > On Wed, Feb 6, 2013 at 10:19 PM, Chip Childers > > <chip.child...@sungard.com> wrote: > > > On Wed, Feb 06, 2013 at 10:10:27PM -0700, Mike Tutkowski wrote: > > >> OK, thanks...I wasn't sure when feature freeze was. > > >> > > >> Do we have a roadmap that might indicate when 4.2 (or whatever it will > be > > >> called) is expected for release? > > > > > > I should probaby put this on the wiki, but we've been planning on going > > > to a 4 month cycle. Here's what we've been working off of: > > > > > > > Would this technically be: > > > > This is a much more accurate way to say it. Thanks Marcus! > > > > 4.1 > > > Nov through Jan - Feature work > > > Feb and March - Testing / Hardening / Wrap-up > > > 4.2 > > > Feb through May - Feature work > > > June and July - Testing / Hardening / Wrap-up > > > 4.3 > > > June through September - Feature work > > > October and November - Testing / Hardening / Wrap-up > > > > ? > >
