Open Stack

Hey Nick, 
I don't know. I've never been a fan of putting install and upgrade in for mation together. They are two separate user processes (although not two different audiences), so you end up bulking the Install Guide, upgrade in for mation is extremely version dependent (hence the typical tagging into release notes), and dev info coming in usually hits at different times as well. 

I think putting it in the wiki is good, is easy to tag just for the Havana page. Will also update the general process in the Ops guide. 

? 
Summer 

----- Original Message -----

> From: "Nick Chase" <nchase at mirantis.com>
> To: "Anne Gentle" <annegentle at justwriteclick.com>
> Cc: openstack-docs at lists.openstack.org, "Summer Long" <slong at redhat.com>
> Sent: Wednesday, December 18, 2013 2:39:40 PM
> Subject: Re: [Openstack-docs] Upgrading to Havana

> Actually it sounds like an installation issue to me. Basically you are
> installing the same version as the install guide, but with the special case
> that you already have the previous version installed.
> On Dec 17, 2013 11:12 PM, "Anne Gentle" < annegentle at justwriteclick.com >
> wrote:

> > On Tue, Dec 17, 2013 at 10:03 PM, Summer Long < slong at redhat.com > wrote:
> 

> > > Hi all,
> > 
> 
> > > Am triaging for bug day, and have signed up to do the upgrade notes
> > > (perhaps
> > > not on bug day, but you know what I mean). However, er, where should they
> > > go?
> > 
> 

> > > Currently, I'm only seeing the notes in the Ops manual, was there a
> > > consensus
> > > to put them somewhere else?
> > 
> 
> > > A new Upgrading article for the Havana page? The Installation Guide is
> > > already too bulky (would think).
> > 
> 
> > > Or have I missed them completely somewhere else?
> > 
> 

> > > Should they also be pulled out of the Ops guide (since upgrading is SO
> > > version-specific)?
> > 
> 

> > I think the job of upgrading usually lands in an operator/architects lap,
> > so
> > I think the Ops Guide is the location. O'Reilly editor thinks so too. It
> > shouldn't be written to be super version specific, though, if it can be
> > helped. Here's the current section:
> > http://docs.openstack.org/trunk/openstack-ops/content/maintenance.html#upgrades
> 

> > I hate to envision this, but I wonder if it could be its own guide? Blah. I
> > stand by my request to have it in the Ops Guide.
> 

> > Anne
> 

> > > thanks, Summer
> > 
> 

> > > --
> > 
> 
> > > Summer Long
> > 
> 
> > > OpenStack Documentation Lead
> > 
> 
> > > Engineering Content Services
> > 
> 

> > > Red Hat Asia Pacific
> > 
> 
> > > Brisbane, Austral ia
> > 
> 
> > > slong at redhat.com | irc: slong
> > 
> 

> > > _______________________________________________
> > 
> 
> > > Openstack-docs mailing list
> > 
> 
> > > Openstack-docs at lists.openstack.org
> > 
> 
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> > 
> 

> > --
> 
> > Anne Gentle
> 
> > annegentle at justwriteclick.com
> 

> > _______________________________________________
> 
> > Openstack-docs mailing list
> 
> > Openstack-docs at lists.openstack.org
> 
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20131217/d23bc02d/attachment.html>