Open Stack

For the API guides, I hesitate to report things that are already either in a project's accomplishments list or a tools update that will also be reported in others release notes.

Any thoughts here? Aggregate info from other teams as a single collection? Or, skip API guide reporting in the common docs release notes?

Looking for input.
Anne

> On Feb 19, 2017, at 7:56 PM, Lana Brindley <openstack at lanabrindley.com> wrote:
> 
> Hi everyone,
> 
> We're now only a couple of days away from release, and we really need to get your release notes in TODAY.
> 
> Still missing are:
> 
> * API Guides
> * Architecture Design Guide
> * Contributor guide
> * High availability guide
> * Installation guide
> * Operations guide
> * Security Guide
> * Training guides
> * Training labs
> * User guides
> * Translations
> 
> If, like me, you've been putting this off, you need to do it TODAY. 
> 
> If you think your guide doesn't need relnotes, please let Mariia, Brian, or myself know, so we will stop hassling you.
> 
> Lana
> 
>> On 03/02/17 21:42, Mariia Zlatkova wrote:
>> Hello specialty team leaders,
>> 
>> 
>> The Ocata release is coming soon and it is time for the release management team to compile the release notes for each doc.
>> 
>> 
>> Replicating what we did with the Newton release, the release management team will be manually compiling the release notes from each of you to be published. Here is the example from Newton: http://docs.openstack.org/releasenotes/openstack-manuals/newton.html
>> 
>> Please report on what major developments have occurred in your respective guides or reference.
>> 
>> 
>> If you have any questions, please contact either me, Brian, or Lana.
>> 
>> 
>> Thanks,
>> 
>> Maria
>> 
>> 
>> -- 
>> *Mariia Zlatkova*
>> Technical Writer | Mirantis, Kharkiv
>> www.mirantis.com <http://www.mirantis.com>
>> 
> 
> -- 
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
> http://lanabrindley.com
>