I vote for cutting OSSN-0013-1 and then, to the extent possible, ensuring that this new one replaces the old one in all of our publication locations. -bryan On Fri, May 30, 2014 at 9:11 AM, Clark, Robert Graham <robert.clark at hp.com> wrote: > Mark Washenberger has pointed out a mistake in OSSN-0013, we should fire > whoever wrote that! > https://bugs.launchpad.net/ossn/+bug/1271426 > > Anyway, we have a few options. > Cut a completely new OSSN that supersedes 0013 and give it a normal number > and add a reference to the no longer valid 0013 > Cut a new OSSN with a number derived from 0013 such as OSSN-0013-1 > > Followed up with what would basically be a revised announcement on –dev > and –security. > > Thoughts? > > > _______________________________________________ > Openstack-security mailing list > Openstack-security at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-security > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-security/attachments/20140530/3a9cd639/attachment.html>