<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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.<br class=""><div class="">
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">~ sean</span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jan 22, 2015, at 3:39 PM, Anne Gentle <<a href="mailto:annegentle@justwriteclick.com" class="">annegentle@justwriteclick.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jan 22, 2015 at 8:36 AM, Roger Luethi <span dir="ltr" class=""><<a href="mailto:rl@patchworkscience.org" target="_blank" class="">rl@patchworkscience.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If we can't branch Juno this week, maybe we should consider<br class="">
merging patches again, as long as they are not specific to Juno or<br class="">
Juno/Kilo-related plans.<br class=""></blockquote><div class=""><br class=""></div><div class="">Curious, what is delaying the branching? </div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
For changes that are good for Icehouse, too, a long freeze (soon to be<br class="">
measured in months) does not seem to make sense. If I remember Andreas'<br class="">
crash course correctly, we could just give infra a commit ID, and they can<br class="">
branch from there even if patches for the new branch have already been<br class="">
merged. All we need to do is agree at some point that all new patches are<br class="">
for the new branch (or must be backported).<br class="">
<br class=""></blockquote><div class=""><br class=""></div><div class="">Yep this is true. </div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Roger<br class="">
<br class="">
_______________________________________________<br class="">
OpenStack-docs mailing list<br class="">
<a href="mailto:OpenStack-docs@lists.openstack.org" class="">OpenStack-docs@lists.openstack.org</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br class="">
</blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature">Anne Gentle<br class=""><a href="mailto:annegentle@justwriteclick.com" target="_blank" class="">annegentle@justwriteclick.com</a></div>
</div></div>
_______________________________________________<br class="">OpenStack-docs mailing list<br class=""><a href="mailto:OpenStack-docs@lists.openstack.org" class="">OpenStack-docs@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<br class=""></div></blockquote></div><br class=""></body></html>