Hi Kyle, I built template and it looks awesome. We are considering to use same approach for Fuel.
My assumption is that spec will be on review for a negotiation time, which is going to be quite a while. In my opinion, it is not always very convenient to read spec in gerrit. Did you guys have any thoughts on auto-build these specs into html on every patch upload? So we could go somewhere and see built results, without a requirement to fetch neutron-specs, and run tox? The possible drawback is that reader won't see gerrit comments.. Thanks, On Sat, Apr 19, 2014 at 12:08 AM, Kyle Mestery <mest...@noironetworks.com>wrote: > Hi folks: > > I just wanted to let people know that we've merged a few patches [1] > to the neutron-specs repository over the past week which have updated > the template.rst file. Specifically, Nachi has provided some > instructions for using Sphinx diagram tools in lieu of asciiflow.com. > Either approach is fine for any Neutron BP submissions, but Nachi's > patch has some examples of using both approaches. Bob merged a patch > which shows an example of defining REST APIs with attribute tables. > > Just an update for anyone proposing BPs for Juno at the moment. > > Thanks! > Kyle > > [1] > https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Mike Scherbakov #mihgen
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
