On 03/15/2013 10:11 AM, Sascha Peilicke wrote:
Hello fellow stackers,
although the official Grizzly release is still some weeks ahead, we should branch Cloud:OpenStack:Master into Cloud:OpenStack:Grizzly in order to reduce the amount of breakage we have the fix every week. Branching (speak copypac'ing) effectively freezes all dependencies contrary to our rolling-release master branch. This alone reduces fallout. Currently, OpenStack compoment version upgrades are commited directly into C:OS:Master for fast turnaround and development times. Contrarily, Cloud:OpenStack:Grizzly is a staging branch and automated updates happen first in Cloud:OpenStack:Grizzly:Staging and are only forwarded to C:OS:Grizzly when unit tests pass. This should help or work on Chef cookbooks, since they can start using C:OS:G as a more stable basis.
In order to keep C:OS:Master in sync, I would add a cronjob that periodically copypac's changed in C:OS:G back until the Grizzly release really happened. This way both OBS projects are kept in sync.
Maybe I should add that this mostly helps to provide a more stable Grizzly repository which cookbooks and tests can be written against. It won't necessarily reduce the effort to fix Grizzly :-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org