Open Stack

Not sure at this point. Pranav was working through Andreas to branch. We wanted to follow the docs team lead on branching, so training-guides can branch with the rest. If I should just be working with Infra rather than overloading Andreas, just let me know.

~ sean

> On Jan 22, 2015, at 3:39 PM, Anne Gentle <annegentle at justwriteclick.com> wrote:
> 
> 
> 
> On Thu, Jan 22, 2015 at 8:36 AM, Roger Luethi <rl at patchworkscience.org <mailto:rl at patchworkscience.org>> wrote:
> If we can't branch Juno this week, maybe we should consider
> merging patches again, as long as they are not specific to Juno or
> Juno/Kilo-related plans.
> 
> Curious, what is delaying the branching? 
>  
> 
> For changes that are good for Icehouse, too, a long freeze (soon to be
> measured in months) does not seem to make sense. If I remember Andreas'
> crash course correctly, we could just give infra a commit ID, and they can
> branch from there even if patches for the new branch have already been
> merged. All we need to do is agree at some point that all new patches are
> for the new branch (or must be backported).
> 
> 
> Yep this is true. 
>  
> Roger
> 
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org <mailto:OpenStack-docs at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs>
> 
> 
> 
> -- 
> Anne Gentle
> annegentle at justwriteclick.com <mailto:annegentle at justwriteclick.com>_______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150122/80853e2b/attachment-0001.html>