<div dir="ltr">Yep, you're on track with what I'm thinking. Prioritize actual incorrect configuration information but otherwise don't backport just to match with master. Make backports the exception not the rule.<div>
<br></div><div>I see this as "perfection is the enemy of the good" also -- which is a judgement call but I think we can make that call pretty soon here. </div><div><br></div><div>Anne</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Dec 18, 2013 at 8:46 AM, Matt Kassawara <span dir="ltr"><<a href="mailto:mkassawara@gmail.com" target="_blank">mkassawara@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Quite a few people seem to use the previous stable release for one reason or another... most likely due to the various packaging mechanisms taking a while to catch up. I would at least like to see the install guide receive patches for issues significant enough to leave the user with a broken system under typical conditions. For example, we should fix an incorrect/missing configuration directive, but not a general clarity/formatting/phrasing problem. However, work on Icehouse documentation should take priority over these patches. I would really like to see the Icehouse install guide work out of the box.</div>
<div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 18, 2013 at 7:26 AM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>On 12/18/2013 03:12 PM, Anne Gentle wrote:<br>
> Hi all,<br>
> I want to propose closing stable/havana in a week or so to start to<br>
> focus on icehouse. I feel we are confusing ourselves especially with the<br>
> many edits to the install guide. At some point you have to walk away and<br>
> I want a judgement call from the team about when that timing is good.<br>
> It's probably after doc bug day 12/20/13.<br>
><br>
> Let me know your thoughts.<br>
<br>
</div></div>What do you mean with closing it off? No more backports at all - or<br>
change the direction from doing nearly all to just the real bad stuff?<br>
<br>
I agree, we should slow down - and my proposal would be to say we only<br>
do it in really exceptional cases. Closing it completely would work as<br>
well...<br>
<span><font color="#888888"><br>
Andreas<br>
--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter: jaegerandi<br>
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>