How else can we parcel out the doc work and track it? Open to any and
all ideas here.
I think a blueprint for the 'Essex Flags' documentation will help track it.
We
can then link bugs to the blueprint, and update the blueprint with any
additional notes or links.
I think a single bug
Yes. This. More below.
On Fri, Mar 30, 2012 at 4:06 AM, John Garbutt john.garb...@citrix.comwrote:
How else can we parcel out the doc work and track it? Open to any and
all ideas here.
I think a blueprint for the 'Essex Flags' documentation will help track
it. We
can then link bugs
Hi Docs Core team and others,
David Kranz has identified changes to the nova.conf configuration options
in the attached .diff file. They directly affect the configuration chapter
for the Compute Admin manual as well as the networking chapter.
I have also gone through all the possible flags and
Maybe filling bugs per flag topics that presents all the related flags ? When one bug matches such, we could mark it as duplicate and refer to the filled bug ?Since there are many flags per topic, that would settle things for the first shot ?Regards
Nuage Co - Razique
On Thu, Mar 29, 2012 at 12:59 PM, Anne Gentle a...@openstack.org wrote:
Hi Docs Core team and others,
David Kranz has identified changes to the nova.conf configuration options in
the attached .diff file. They directly affect the configuration chapter for
the Compute Admin manual as well as the
5 matches
Mail list logo
