<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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 ?<div>Since there are many flags per topic, that would settle things for the first shot ?</div><div>Regards</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Helvetica; "><b style="color: rgb(19, 112, 138); ">Nuage & Co - Razique Mahroua</b></span><span class="Apple-style-span" style="color: rgb(19, 112, 138); font-family: Helvetica; "><b> </b></span><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; font-style: normal; "><font class="Apple-style-span" color="#13708a"><a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a></font></div></span><br class="Apple-interchange-newline"><span></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; font-style: normal; "></span><span style="color: rgb(0, 0, 0); font-weight: normal; "></span></span><span><img height="125" width="125" id="857d757e-c41c-4a15-85f8-faf08f775f04" apple-width="yes" apple-height="yes" src="cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique"></span>
</span></span></span></div>
<br><div><div>Le 29 mars 2012 à 21:59, Anne Gentle a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Docs Core team and others, <br>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. <br>
<br>I have also gone through all the possible flags and created this list: <a href="http://etherpad.openstack.org/newflagsessex" target="_blank">http://etherpad.openstack.org/newflagsessex</a> indicate what are new in Essex. <br>
<br>I realize this is a lot of work and I'd like ideas for how to track the doc work for all these changes. My sense is that many are already logged as doc bugs so possibly I just log more bugs based on groups of flags. <br>
<br>So, no my question. Should I log new doc bugs for each these?<br>
<br>logging options changes<br>networking options changes<br>credentials options changes<br>monkey patching for eventlet/greenlet options<br>S3 SSL options<br>Netapp options<br>Kombu options<br>zone options: default Scheduler zone option, fill first option, least cost<br>
new images and Glance options<br><br>There are already doc bugs logged for these options:<br>nova api options (<a href="https://bugs.launchpad.net/openstack-manuals/+bug/705070">https://bugs.launchpad.net/openstack-manuals/+bug/705070</a>)<br>
LDAP options changes (<a href="https://bugs.launchpad.net/openstack-manuals/+bug/953132" target="_blank">https://bugs.launchpad.net/openstack-manuals/+bug/953132</a>)<br>
Linux bridging options (<a href="https://bugs.launchpad.net/openstack-manuals/+bug/953151" target="_blank">https://bugs.launchpad.net/openstack-manuals/+bug/953151</a>)<br>policy options (<a href="https://bugs.launchpad.net/openstack-manuals/+bug/922147" target="_blank">https://bugs.launchpad.net/openstack-manuals/+bug/922147</a>)<br>
<br>How else can we parcel out the doc work and track it? Open to any and all ideas here. <br><br>Thanks,<br>Anne<br><br><br><br>
<span><diablo-essex-flags-diff></span>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></body></html>