Good timing, I was about to send a follow-up email about this spec. 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. 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? Thoughts? Darren
On Friday, 18 November 2016, 13:33, Lana Brindley
<openst...@lanabrindley.com> wrote:
Isn't that more or less what this is?
https://review.openstack.org/#/c/394261/
L
On 18/11/16 11:36, Steve Martinelli wrote:
> In the keystone docs we have notes about how to upgrade between releases [1],
> so does the nova team [2].
>
> Is it time we create an official guides to [3] for this subject?
>
> [1] http://docs.openstack.org/developer/keystone/upgrading.html
> [2] http://docs.openstack.org/developer/nova/upgrade.html
> [3] http://docs.openstack.org/
>
>
> _______________________________________________
> OpenStack-docs mailing list
> openstack-d...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
--
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
_______________________________________________
OpenStack-docs mailing list
openstack-d...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
