Be more informative when putting -2 for stable freeze
At the moment, if authors of backports are not aware of stable maintainance policy, they are left with action items to overcome the freeze. We should provide all the needed info to proceed with backports for the upcoming stable release. The text is adopted from: https://wiki.openstack.org/wiki/StableBranch#Stable_release_managers Change-Id: I657e7ef401c380fd6e6122a25c2eecbd63d57c24
This commit is contained in:
parent
1bbf15a1be
commit
b7db851295
@ -129,9 +129,21 @@ class Revision(object):
|
||||
return '%s # %s' % (self.change, self.url)
|
||||
|
||||
|
||||
FREEZE_MSG = r"""
|
||||
stable/%s freeze for %s
|
||||
|
||||
The stable branch is frozen to allow testing before the release. Freeze
|
||||
exceptions can be proposed on openstack-dev mailing list with [stable] tag in
|
||||
subject. Once exception request is sent, stable-maint-core team will try to
|
||||
reach consensus.
|
||||
|
||||
More details at: https://wiki.openstack.org/wiki/StableBranch
|
||||
"""
|
||||
|
||||
|
||||
def freeze(reviews, rel):
|
||||
logging.info('freezing %s reviews.' % len(reviews))
|
||||
msg = 'stable/%s freeze for %s' % (openstack_release(rel), rel)
|
||||
msg = FREEZE_MSG % (openstack_release(rel), rel)
|
||||
frozen = []
|
||||
for review in reviews:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user