On Thu, 2015-02-26 at 14:18 -0600, Anne Gentle wrote: > Do the features listed in the Release Notes each have appropriate > documentation? So far we just link to the specifications for nova, for > example.  So to me, it could be a focus on the specification > acceptance means less time/energy for the actual user-facing docs. > Great question. I have no idea of how we can correlate blueprints/specs completed and the existence of accompanying doc. The tool we have now scans git repositories and launchpad (will soon scan storyboard, too): what data is in there that this tool can use to guess documentation coverage?
Happy to brainstorm this with you and Bitergia's Jesus and Daniel as they may have ideas. /stef __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev