> > 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 for each group of options will probably suffice; there > will > only be a few people working on this anyways.
Can automate that? Maybe get Jenkins, when it merges a branch, to raise a doc bug if a new flag has been added, or the flag comment or default has changed? You might get a few false positives, but that is probably no bad thing. Cheers, John _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
