I generally lean toward blueprints to manage a group of similar patches that involve content updates rather than bugs. On Thu, Sep 11, 2014 at 12:06 PM, Nicholas Chase <nchase at mirantis.com> wrote: > > On 9/11/2014 3:15 AM, Andreas Jaeger wrote: > > If you need something to keep track, we can also use an etherpad or wiki > page. I consider a separate bug for each issue a lot of overhead, Andreas > > > I forget sometimes that we said you can do patches without an associated > bug. :) > > -- > Nick Chase > 1-650-567-5640 > Technical Marketing Manager, Mirantis > Editor, OpenStack:Now > <http://openstacksv.com> > > _______________________________________________ > Openstack-docs mailing list > Openstack-docs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/dcc9039c/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: www.openstacksv.com_.png Type: image/png Size: 7160 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/dcc9039c/attachment-0001.png>
