On Mon, Sep 15, 2014 at 4:52 AM, Kevin Benton <blak...@gmail.com> wrote: > I saw that the specs that didn't make the deadline for the feature freeze > were removed from the tree completely. For easier reference, can we > instead revert that commit to restore them and then move them into a release > specific folder called 'unimplemented' or something along those lines? > No, I don't think there's value to keeping specs along which never made a release. The point of the specs repo is to track things which made the release.
> It will be nice in the future to browse through the specs for a release and > see what specs were approved but didn't make it in time. Then if someone > wants to try to propose it again, their patch can be to move the spec into > the current cycle and then they only have to make revisions rather than redo > the whole thing. > It should be easy to re-propose the specs for inclusion in Kilo once that opens up. You can grab a version of the repo before the removal commit, pull out the spec, update it and re-propose it. > It also reduces the number of hoops to jump through to quickly search for a > spec based on keywords. Otherwise we have to checkout a commit before the > removal and then search. > > Thoughts, suggestions, or anecdotes about small sailboats? > > 1. > https://github.com/openstack/neutron-specs/commit/77f8c806a49769322b02ea6017a1a2a39ef1cfd7 > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev