Open Stack

On Tue, 2013-03-12 at 10:12 +0100, Thierry Carrez wrote:
> Mark McLoughlin wrote:
> > On Tue, 2013-03-12 at 09:20 +0200, Gary Kotton wrote:
> >> Hi,
> >> Is there any chance to get a planned release date for OSLO RC-1.
> > 
> > That was my plan, but the date crept up on my. Will try and get it done
> > today.
> > 
> >> This 
> >> would enable the project using OSLO to pull in the latest changes and 
> >> ensure that we all have a synced snapshot of the OSLO release.
> > 
> > All projects are using 1.1.0b1 and there have been no changes since.
> 
> I think Gary's question is linked to the incubator, not oslo-version...
> When are we declaring Oslo grizzly "done" so that all projects can have
> a synced snapshot of the latest incubator state ?

Projects should sync regularly. There's no reason to wait for anything
to be considered "done".

> Since we don't really "release" anything from the incubator, it's more a
> question of when we are moving to only-critical-bugs mode. We could cut
> a stable/grizzly branch at that point (and let master continue to
> havana). Then we only update.py from stable/grizzly and make sure that
> if we change anything in stable/grizzly we sync that to all relevant
> projects.

Well, oslo-incubator is in feature freeze like other modules.

I don't see the need to be ultra proactive in syncing to all projects
every time there's a change in oslo-incubator. In only-critical-bugs
mode, we should only be syncing to a given project when we know the sync
fixes a critical bug. Otherwise the sync is just needless risk.

Cheers,
Mark.