How about top-level organization by project/service, each with consistent
topics that pertain to installation, configuration, upgrades, development,
API, etc? Projects can determine whether some or all of those topics reside
in the openstack-manuals or project repository.
On Fri, Nov 18, 2016 at
Excerpts from Steve Martinelli's message of 2016-11-17 20:36:46 -0500:
> 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]
[mailto:s.martine...@gmail.com]
Sent: Thursday, November 17, 2016 5:37 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>; openstack-d...@lists.openstack.org
Subject: [openstack-dev] [docs][upgrades] time to add official docs for
upgrading se
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]
