Another file in our repo is just to provide this review mechanism for now. All deliverables has to follow governance procedures as well.
On 24 January 2017 at 12:04, Doug Hellmann <[email protected]> wrote: > Excerpts from Ian Cordasco's message of 2017-01-24 14:55:31 -0500: >> -----Original Message----- >> From: Michał Jastrzębski <[email protected]> <[email protected]> >> Reply: OpenStack Development Mailing List (not for usage questions) >> <[email protected]> <[email protected]> >> Date: January 24, 2017 at 11:01:14 >> To: OpenStack Development Mailing List (not for usage questions) >> <[email protected]> <[email protected]> >> Subject: Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable >> >> > Hello everyone, >> > >> > We've reached our agreement! >> > http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_28264d5a40d0088c >> > New deliverable process will be lightweight - just normal +2+2+PTL >> > vote is needed to add new deliverable. I'm going to create new >> > deliverables.yaml file in Kolla repository which will allow us to keep >> > track of deliverables. Review incoming:) >> >> Is Kolla not using openstack/releases to track deliverables? If so, why >> duplicate that information? >> >> -- >> Ian Cordasco > > They need to be listed in openstack/governance in order to count for > elections. > > Doug > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
