[openstack-dev] [ptls][all][tc][docs] Documentation migration spec
doug at doughellmann.com
Fri Jun 23 14:09:44 UTC 2017
> On Jun 23, 2017, at 8:57 AM, Renat Akhmerov <renat.akhmerov at gmail.com> wrote:
> I can say for Mistral . We only planned to add Mistral docs to the central repo but didn’t do it yet. So, as far as I understand, we don’t need to move anything. We’ll review the spec and adjust the folder structure according to the proposed.
Please do review the steps in the spec. Not all of them are about moving content. There are steps for setting up the new build job so that the content will be published to the new URLs as well.
> Renat Akhmerov
> 23 июня 2017 г., 3:32 +0700, Doug Hellmann <doug at doughellmann.com>, писал:
>> Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +0000:
>>> Hi everyone,
>>> Doug and I have written up a spec following on from the conversation  that we had regarding the documentation publishing future.
>>> Please take the time out of your day to review the spec as this affects *everyone*.
>>> See: https://review.openstack.org/#/c/472275/
>>> I will be PTO from the 9th – 19th of June. If you have any pressing concerns, please email me and I will get back to you as soon as I can, or, email Doug Hellmann and hopefully he will be able to assist you.
>>>  http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html
>> Andreas pointed out that the new documentation job will behave a
>> little differently from the old setup, and thought I should mention
>> it so that people aren't surprised.
>> The new job is configured to update the docs for all repos every
>> time a patch is merged, not just when we tag releases. The server
>> projects have been working that way, but this is different for some
>> of the libraries, especially the clients.
>> I will be going back and adding a step to build the docs when we
>> tag releases after the move actually starts, so that we can link
>> to docs for specific versions of projects. That change will be
>> transparent to everyone else, so I have it on the list for after
>> the migration is under way.
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev