Open Stack

> On 30 Jun 2016, at 16:07, Steven Dake (stdake) <stdake at cisco.com> wrote:
> 
> Hey folks,
> 
> I am keen on tagging Kolla in the governance repository with every tag that is applicable to our project.  One of these is release:managed.  I've been working as PTL the last 3 cycles to get Kolla processes to the point we could apply for release:managed.  Looks like Doug and release team in general has beat me to the punch :)
> 
> The requirements of the tag are met by force because of how the release process is now executed.  I'm wondering if this tag has any meaning any longer given the fact that the release team has nearly automated themselves out of a job :)

I think you fall under wrong perception of the level of automation here. That’s ok, I also did before. :)

While openstack/releases repo indeed allows to post release patches for all official projects, there is an assumption that e.g. the git tag for the release is signed and pushed by the project respective release liaison. In that way, the openstack/releases patch is just for documentation purposes, it does not trigger actual release (because it happened before with the git tag being pushed).

Note that while there is that expectation, release team is usually very helpful and will check the tag, and if there is no tag yet, will push it for you. But that’s not supposed to be the default behaviour.

> 
> If it does have some special meaning or requirements beyond the "we will freeze on the freeze deadline" could someone enumerate those?
> 
> FWIW I feel a lot more comfortable with the current release process.  The release team has done a fantastic job.  I always felt nervous pushing a signed tag and I've been doing this for ~5 years :)
> 
> Regards
> -steve
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev