Doug,
Thanks for the resolution. It is well written and sets appropriate guidelines.
I was expecting something terrible – I guess I shouldn’t have expectations
ahead of a resolution. Apologies for being a jerk on the ml.
Nice work.
I left some commentary in the review and left a vote of -1 (just a few things
need tidying, not a -1 of the concept in general).
Regards
-steve
-Original Message-
From: Doug Hellmann
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, May 30, 2017 at 2:54 PM
To: openstack-dev
Subject: [openstack-dev] [tc][kolla][stable][security][infra][all]
guidelines for managing releases of binary artifacts
Based on two other recent threads [1][2] and some discussions on
IRC, I have written up some guidelines [3] that try to address the
concerns I have with us publishing binary artifacts while still
allowing the kolla team and others to move ahead with the work they
are trying to do.
I would appreciate feedback about whether these would complicate
builds or make them impossible, as well as whether folks think they
go far enough to mitigate the risks described in those email threads.
Doug
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/116677.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117282.html
[3] https://review.openstack.org/#/c/469265/
__
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
__
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
