Argument naming ambiguity led to grabbing the wrong value. This updates
repo name handling to grab from the right input.
Change-Id: I4987fc012a07344cbc4290e33eae5b772270eb07
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
We use release-types as a way to verify that versions are compatible and
if needed reflected accurately in the code (puppet, xstatic). If one
isn't set explicitly then we assume python-service.
In certain circumstances (anything other than the first release in a
series) we also perform python specific requirements checking on all
'python' types.
Add a new 'generic' type that uses the same rules to validate version
numbers but wont run any python specific checks.
We need this a projects (like monasca-thresh) will fail the requirements
check for 2nd or greater releases[1].
An alternate would be to have the requirements code check if setup.py
exists before calling it but that seems like the wrong layer to me.
[1] http://logs.openstack.org/54/652854/1/check/openstack-tox-validate/80df01c/job-output.txt.gz#_2019-04-16_06_08_00_636538
Change-Id: I3fcde5eb266f954fddb6871ce8690b93b8fd7a8d
This is to pick up [1], which is needed by [2].
Although nothing feature-y has happened since 3.13.1, this is done as a
"feature" release because it's the first in Train and we need to leave
room for 3.13.2+ in Stein.
[1] https://review.openstack.org/#/c/644251/
[2] https://review.openstack.org/#/c/643601/
Change-Id: I8b32707bee7d39a7c699bf52375692f50bcde114
This is a procedural review to tag a final release for each deliverables ; and
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: I0ea3e30572fb745950c0eca0770f96bb87e0a53b
A number of changes have landed in neutron-lib since 1.25.0 so let's
release 1.26.0 so we can consume them now that we are in Train.
Change-Id: Id55d7b5c5d099782d8b90d07922496a27b389ddd
This is a procedural review to tag a final release for each deliverables ; and
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Don't create a new release for requestsexceptions as there aren't any
functional changes since 1.3.0
Change-Id: I9df31bd92ccf7613f708aef280024b8faf451bab
This is a procedural review to tag a final release for each deliverables ; and
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: Id45db7659fff33cfac66f7e346c69d682ff3a718
The stable/pike branch for mistral-lib was created at 0.2.0 but in
I0a8bb59c35aec40ae529fce5da6f30f3820991af, I mistakenly approved the
change to switch that to 0.3.0.
Set it back to the correct branch point
Change-Id: I34e053831eba3d015566242bc91894da6c27ff8f
This is a procedural review to tag a final release for each deliverables ; and
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: I6d72c57fdc58623a7ce89d6320d703b1acfd6210
