The new way of packaging a python project is via build package. This
patch replaces the old setup.py style sdist and wheel build.
Change-Id: I67cbdfdfd9ed334e742ff4def21c59cd8a8de24c
hacking 6.0.0 release contains flake8 5.0.4, which started to show the
following error:
./openstack_releases/versionutils.py:54:14: E275 missing whitespace after keyword
yield('Version %s looks like a pre-release and the release '
This patch adds a whitespace after the 'yield' keyword to make the pep8
job pass.
Change-Id: I433ccb6a31cc450a666673374b78dcc1fea1bb7b
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not handled in the propose-final-releases command as
it still uses the release name. This patch fixes this by reading the
'release-id' field from series_status.yaml and if present then uses it
as stable/<release-id> for the branch creation.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: Ie8ba3e9bfa01148e93f5920050703e998248db11
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not handled in check_branch_sha method
in validate.py, as the method still searches stable/$series.
This patch fixes this by reading the 'release-id' field from
series_status.yaml if present and uses it as stable/<release-id>
for the branch search.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: I014b1d6dc561be4db0fc8faa85fb3133e851acfc
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not handled in the list-deliverables command as it
still uses the release name. This patch fixes this by reading the
'release-id' field from series_status.yaml and if present then uses it
as stable/<release-id> for the branch creation.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: Id6a03024fa2268ba233189abfe48556d3530daef
Independent projects do not have "stable" branches, so the
new_release script will fail.
Set version to master and change it accordingly only if it's not
and independent project.
Change-Id: I9ba7f251d64e2bfca5c262acf9b20dc3da23fc87
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not accepted in the validator command.
Previously the validator was fixed for 'std' and 'std-with-versions'
branching typed deliverables, but missed the 'tagless' deliverables
case. This patch fixes this by accepting the new branch naming style,
stable/<release-id>, for tagless deliverables, too.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: I6ba51454213e095e6b76e0813dab3ce44b1457ba
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not handled in the new-release command as it
still uses the release name. This patch fixes this by reading the
'release-id' field from series_status.yaml and if present then uses it
as stable/<release-id> for the branch creation.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: Ic9888b74b398d14f2a1dc5b6d30bca5f23493b5b
With the new release identification / naming schema [1] (like:
2023.1 Antelope) new stable branch naming was introduced (like:
stable/2023.1). This was not handled in the propose-library-branches
command as it still used the release name. This patch fixes this by
reading the 'release-id' field from series_status.yaml and if
present then uses it as stable/<release-id> for the branch creation.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: Ie87862669fb965729e23a9374c34b1ba2e71b445
For projects that has branch type 'std-with-versions' (like ironic,
because they cut bugfix/<MAJOR>.<MINOR> bugfix branches) the new stable
branch name style (like stable/2023.1) does not pass validator. This
patch extends the validator to accept these branch names, too.
Change-Id: If597684b1a4ea741707ee786e8e01e9e8f3d2cb4
The new release identification / naming schema [1] (like:
2023.1 Antelope) broke the redirection rules for branch specific upper
constraint files as the stable branch names are from now on based on
the new release identification (like: stable/2023.1).
This patch fixes the redirections by introducing the release ID field
to series status, to translate a release name to 'stable/<release-id>'
where this ID exists.
[1] https://governance.openstack.org/tc/reference/release-naming.html
Change-Id: Iab885d4e36f64903b323e16c74d8315c759584de
This fix aim to solve issues with the new naming convention related to
SLURP releases.
Without that our validation will fail to validate stable branches named
like `stable/2023.1`.
Change-Id: Ic45d4a13f63846e5b60bde800492da7c851addf8
This patch adds to the Releases page template the possibility to
indicate whether a release is a SLURP release.
Change-Id: Ie0dcddfe271e8fd77a6d40fa54c8ef2ee6914b78
Validation is not needed for a series as soon as it reaches the
Extended Maintenance state as there won't be any releases from such
branches. This patch updates the set of closed series to avoid
unnecessary validation.
Change-Id: I0f093865bab190273421d966c755434d0369e0a0
When the latest branch cut is from the very same hash as the previous
branch was cut from, then the rev-list gives an empty list. Originally
the last item from the list should have been taken. Since the list is
empty the splitlines()[-1] gives "IndexError: list index out of range".
This patch fixes this case with returning None early.
Change-Id: If5ea4a356b0c7620e2de1d2ab77951d8b76bb5e2
The validate_pypi_permissions test checks that if the package exists on
PyPI, we have permissions to upload it. In order to validate that, it
first checks that the package exists by retrieving JSON information from
PyPI, and assuming that anything returned means the package exists.
However currently PyPI returns {'message': 'Not Found'} when queried for
JSON information about a non-existant package. This makes the test
assume that the package exists but we don't have permissions to upload
it, therefore failing the test.
This fix makes sure an empty dict is returned when an inexistant package
is queried, which makes the test succeed with the following message:
'no %s project data on pypi, assuming it will be created by release'
Change-Id: I27eb82109ab93fe33c339f82ec519feeb7228a1f
With the recent switch to using the build utility, this should no
longer be necessary. Even more recent changes in the Python
packaging toolchain seem to have made it stop working anyway, so
remove it and treat PBR's builds like any other project.
Change-Id: I6f9a4546fb6a7b2a4836d6aeea0713f7a7da3002
With the latest upper constraints updating generated patch [1] the
openstack-tox-docs job started to fail, due to conflict:
ERROR: Cannot install jsonschema<4.0.0 and >=3.2.0 because these
package versions have conflicting dependencies.
The conflict is caused by:
The user requested jsonschema<4.0.0 and >=3.2.0
The user requested (constraint) jsonschema===4.7.2
This is because we have jsonschema<4.0.0 in our requirements.txt.
By uncapping the constraint the docs job is passing.
Date validation needed to be updated as well, because a deprecated
usage of validator extending method was used in the code, which was
removed [2] from jsonschema with the 4.0.0 release. This patch replaces
that with adding a TYPE_CHECKER instead.
With the new jsonschema constraint openstack-tox-py36 job does not pass
anymore, but py36 is dropped from zed anyway. That job is pulled in by
an old job template, which needs to be replaced to the new zed job
templates, too.
[1] I89576353371aa87d181610eb6242cbe961487af6
[2] d9f6384060
Closes-Bug: #1982757
Change-Id: Ida6310dd822e587ce9c424a228fdff5192ba0476
Validation is not needed for a series as soon as it reaches the
Extended Maintenance state. This patch updates the set of closed series
to avoid unnecessary validation. Together with Victoria, now this patch
adds older series, too, that were missed at their transition time.
Change-Id: I3f2b98540757a2370a923d71f8a38e15fbe35985
A missing comma was causing the strings to be concatenated,
resulting in a wrong command that caused the validate job
to fail.
Change-Id: I7c5dab48db725608c7b1cfa4e8e8034d8225b165
The new way of packaging a python project is via build package. This
patch replaces the old setup.py style sdist and wheel build.
Change-Id: Ia351d099aa3b2491e3a4d255d87bb7c6bd691cac
The TC tags framework is discontinued [1], so all references to
TC tags will be invalidated once TC passes the change.
This patch removes these references to avoid breaking the releases
repo.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027214.html
Change-Id: Idf5cddc7d1a535e1a9bcc2c2922cf23c3a8d539b
These teams are PTL-less and not necessary define their
release liaison openstack/release/data/release_liaison.yaml.
The problem is that their official reviewers arn't necessarly
detected.
These changes allow to consider these release liaisons folks.
Change-Id: I29295dddb2619043a43957e5e2c2f64d0787784b
Without knowing which releases have been made within the given
series either we shoots in dark in choising the kind of release
(bugfix, feature, major, etc...) or we need to check manually
what are the existing versions. That's time consuming.
These changes simply display the current versions available in
the given series.
Change-Id: Idb160198d52d3bc6b0fa00095b143b19a1f130eb
We recently observed that this check was skipped. Indeed it was
possible to propose a bugfix version on the first release of a series
without facing validation errors [1].
The described situation was allowed by checks that we introduced
during Wallaby [2]. Those was designed to ensure that we can
build sdist from the proposed tag. Indeed, they temporarly created
the new git tag to build sdist from it. However we never delete this
tag after our tests so this temporary tag is see as an existing tag
and so that led us to the observed bug.
Our validation check that the first version number of series isn't a
bugfix after it tried to build the sdist from the new tag, so, without
this patch the tag newly created by the sdist check remains available
in the repo, and so a couple of next checks are skipped, including the
validation of the version number, because these checks are decorated
to ignore existing tags.
Indeed the function decorated with `skip_existing_tags` detect this
temporary tag as an existing tag, so, the decorated functions are
skipped.
We should notice that it surely impacted other checks in the same manner.
Indeed, all validation functions decorated with this function
`skip_existing_tags` are impacted by this bug.
Hopefully it didn't have too much side effects.
These changes delete the temporary tag after usage to ensure to restore
the initial environment and to stop skipping next checks.
[1] https://review.opendev.org/c/openstack/releases/+/795836
[2] 80652b5232
Change-Id: I5d9024528d08487a7582e0a0e73576b22708a6cf
When validating PyPI settings, we retrieve package roles. If that
retrieval is not successful on the first try, we immediately retry
with a canonicalized version of the package. This sometimes hits
PyPI ratelimits. This patch introduces a one second sleep to avoid
that error.
Change-Id: Ifd20200159a2f136827a1987606b650a6db5588f
Last tag was created more than 2 years ago since
then master have included couple of features and
bug fixes. It would be good to get a tag release
for current master and also a stable/2.0 to backport
fixes into it.
Add stable-branch-type: upstream to allow
naming scheme apart from openstack release names.
Also add seperate release type for openstack-virtual-baremetal
as it's not publishing other pypi or tarball artifacts.
Change-Id: Ia8c9c5e8ad577f6ec1796591e77fddaffa62f008
This tool will be used in doc addition around the branching period
to ensure that we don't miss to create stable branches for project.
Also this tooling should be used around each trailing deadline to ensure
to not forget a trailing projects. Trailing projects are those who can
easily meet the conditions that lead to forget to branch them.
Adding usage of this tooling in our process to ensure to check that
point once a time at each new series.
Change-Id: I2a8bd25ecfe5bb1bde5af16b08f897a5bdc11cb7
Adding validation check to ensure that we are able to build sdist from
the latest tag.
This will allow us to detect sooner when we will try to add a tag to a branch
which is older than another tag already on that branch/in that branch's history
Indeed we recently experienced similar issue [1] with os-collect-config and
tripleo-ipsec where projects hadn't been branched for ussuri [2] and where
we tried to create a new ussuri release [3] on the same hash that an
existing wallaby tag.
Projects have been branched [3] after tags creation [2].
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.html
[2] 688914aa29
[3] ihttps://review.opendev.org/c/openstack/releases/+/772047
Change-Id: Ie2d055f171418e2d35db697dfb1aa17cd449bea9