<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1479267575590_961818"><span id="yui_3_16_0_ym19_1_1479267575590_962347">Good timing, I was about to send a follow-up email about this spec.</span></div><div id="yui_3_16_0_ym19_1_1479267575590_961818"><span><br></span></div><div id="yui_3_16_0_ym19_1_1479267575590_961818"><span id="yui_3_16_0_ym19_1_1479267575590_962419">I agree, this content needs to be more visible, which is why the spec proposed to move upgrade notes to the Upgrades chapter in the Operations Guide. However, it seems like the general consensus is to keep content in project repos because it is more likely to be maintained there. </span></div><div id="yui_3_16_0_ym19_1_1479267575590_961818"><br></div><div id="yui_3_16_0_ym19_1_1479267575590_961818"><span id="yui_3_16_0_ym19_1_1479267575590_962704">Considering the Ocata development cycle is pretty short, we've already established our docs deliverables, and other projects are still developing upgrade notes, would links to the upgrade notes in the Ops Guide suffice in the interim? We can then propose and plan a better solution for Pike, such as in-tree official guides? </span></div><div id="yui_3_16_0_ym19_1_1479267575590_961818"><span><br></span></div><div id="yui_3_16_0_ym19_1_1479267575590_961818"><span>Thoughts?</span></div> <div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1479267575590_961769"><br></div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1479267575590_961769">Darren</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1479267575590_961769"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1479267575590_961768" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 13px;" id="yui_3_16_0_ym19_1_1479267575590_961767"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1479267575590_961766"> <div dir="ltr" id="yui_3_16_0_ym19_1_1479267575590_962080"><font size="2" face="Arial" id="yui_3_16_0_ym19_1_1479267575590_962079"> On Friday, 18 November 2016, 13:33, Lana Brindley <openstack@lanabrindley.com> wrote:<br></font></div> <br><br> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1479267575590_961765">Isn't that more or less what this is?<br clear="none"><br clear="none"><a shape="rect" href="https://review.openstack.org/#/c/394261/" target="_blank" id="yui_3_16_0_ym19_1_1479267575590_961764" class="edited-link-editor">https://review.openstack.org/#/c/394261/</a><br clear="none"><br clear="none">L<br clear="none"><div class="yqt4211846700" id="yqtfd66938"><br clear="none">On 18/11/16 11:36, Steve Martinelli wrote:<br clear="none">> In the keystone docs we have notes about how to upgrade between releases [1], so does the nova team [2].<br clear="none">> <br clear="none">> Is it time we create an official guides to [3] for this subject?<br clear="none">> <br clear="none">> [1] <a shape="rect" href="http://docs.openstack.org/developer/keystone/upgrading.html" target="_blank">http://docs.openstack.org/developer/keystone/upgrading.html</a><br clear="none">> [2] <a shape="rect" href="http://docs.openstack.org/developer/nova/upgrade.html" target="_blank">http://docs.openstack.org/developer/nova/upgrade.html</a><br clear="none">> [3] <a shape="rect" href="http://docs.openstack.org/" target="_blank">http://docs.openstack.org/</a><br clear="none">> <br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> OpenStack-docs mailing list<br clear="none">> <a shape="rect" ymailto="mailto:OpenStack-docs@lists.openstack.org" href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br clear="none">> <a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a></div><br clear="none">> <br clear="none"><br clear="none">-- <br clear="none">Lana Brindley<br clear="none">Technical Writer<br clear="none">Rackspace Cloud Builders Australia<br clear="none"><a shape="rect" href="http://lanabrindley.com/" target="_blank">http://lanabrindley.com</a><div class="yqt4211846700" id="yqtfd08583"><br clear="none"></div><br><div class="yqt4211846700" id="yqtfd65096">_______________________________________________<br clear="none">OpenStack-docs mailing list<br clear="none"><a shape="rect" ymailto="mailto:OpenStack-docs@lists.openstack.org" href="mailto:OpenStack-docs@lists.openstack.org" id="yui_3_16_0_ym19_1_1479267575590_976269">OpenStack-docs@lists.openstack.org</a><br clear="none"><a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank" id="yui_3_16_0_ym19_1_1479267575590_976271">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>