When patching ACL files, rather than just add a section for
stable/$newseries, we should also delete old stable/$series
sections. Otherwise around $newseries release time,
stable/$series would be owned by release managers again.
Change-Id: I1fdc8e370f0f56df54ba27736046d7d6893ca240
The only reason we have a dependency on launchpadlib and
lazr.restfulclient is for the old tool that imported project history
from launchpad. We no longer need the tool, so we can remove it and the
dependency as part of our python 3 port.
Change-Id: Ie87e6172c953df10cb70d34c9bc23ad30e97ce4d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
If we get a validation error, report it and skip the version.
Change-Id: Id2117405d10efaaa74cf23faa8720e9f66c5eb00
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
When importing history for an independant project currently
tag_history_from_git will create the file in
deliverables/UNKNOWN/$project.yaml. Add a series argument so the file
can be created in the correct directory.
Change-Id: I22c840d1b46624bfdef8add09718c4dc4e489917
If the existing link matches the expected link, leave it in place
regardless of where it is in the file.
If the link needs to be updated, try to insert the link after the
"team" entry, assuming that will be closer to the top of the file
than "releases" and avoiding the need to figure out if "branches" comes
before or after "releases".
Change-Id: I4161bb048deba91ccf8170ea5f0b7208bd9a80a3
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The script creates a separate output file for each team because
combining all of the data into one makes it to big to post on a
pastebin.
Change-Id: Ie5bfb0df225378e658ebb3c5d57d55d0dff7aca6
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Use a version of list_unreleased_changes.sh that does not rely on the
release-notes command from the release-tools directory.
Change-Id: Ifab8585a3707927d224ee223a551167cced05261
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We had at one case where the release validation logic failed to catch a
release from master after the stable/ocata branch was created for
mox3. This script looks at the other "late" releases, created after a
branch, and verifies that they are all on the correct branch.
Change-Id: Ie148a34efa029e6715db099f7e5c9575ed94238d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Print the names of the files we expect to be updating for each project
as they are found, since some repositories may use the same file for
permission settings.
Change-Id: I1a18d6916b99c6c5ce55306a6d9d13ecac4973bd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Instead of requiring the series argument, look at the default that the
rest of the scripts use. There is still a command line option for
overriding the default.
Change-Id: I7168b4786ac8f275da1ff0cd177268b3a4c20c17
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update the portion of aclmanager that modifies the gerrit groups to pull
the list of repositories properly.
Change-Id: Ib4b78de738517e9d6bd9176a9e4ad61203f22036
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The aclmanager script needs to be able to get a list of repositories
with the cycle-with-milestone release model, and the data for that lives
in this repository now instead of the governance repository. Rather than
having a tool that relies on this data live in release-tools, move it
here.
Change-Id: I7c2c54c4949829aea92e569e3ac9ec9007d932ed
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Instead of building the RST table, build a YAML input data file to be
used with the new schedule rendering template. The results will have to
be edited by hand, but we at least get the dates and fixed events
included for free.
Change-Id: I3cc38afd80eb41200c7269a3039e87f01156eaab
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Find the versions for which the stable branches were created and update
the deliverable files with the historical info.
Change-Id: Idb233e0ec78f2b7ea0f07d596d6452786f725315
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
release.sh no longer processes the send-announcements-to
directive, so stop requiring it.
Change-Id: I53224100b821416f01ebbd5396b4fd9f632b2489
Depends-On: I37f24fe4a716c9b64f241d7a45da8e8bce8b55c2
As per OpenStack licensing guide lines [1]:
[H102 H103] Newly contributed Source Code should be licensed under
the Apache 2.0 license.
[H104] Files with no code shouldn't contain any license header nor
comments, and must be left completely empty.
[1] http://docs.openstack.org/developer/hacking/#openstack-licensing
Change-Id: I9f4673f19ce045a2aad656fdc27679a8ada23ff7
Add a step to the release process to ensure that the note links are
pointing to the right pages, and update the tool used to do that so it
is more robust.
Change-Id: I7beb85f63212c4ca696c9012b673e4d1b2b6d453
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The release schedule is no longer bounded by the summit, so don't
include it.
Add 2 weeks for the cycle-trailing deadline.
Change-Id: I8bca376d910c218b65a29d2e400fd519348f73b9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
When trying to use the history import tools we need to use the correct
release-type setting to validate tags.
We can't use versionutils.validate_version() as it's a generator which is
hard to use in a sorted() function. Insetad introduce
versionutils.canonical_version() which will return the version is valid
or raise a ValueError() exception.
Change-Id: If10aab4c573342227e2909fd84f843c96f3abc43
The project team name is no longer a great default for when importing
history. Use the 'basename' of the git repo we're importing instead.
Change-Id: I2ee75f116101d5712bd2fdc821c4f9bc3e60e2d0
We mandate team and send-announcements-to tags in the yaml file but the
tools to import history don't supply them.
Fix that.
Change-Id: Id9edd21634a500949caed45cf7990ccde0264d73
Teams add and remove repositories, change owners of repositories, and
are themselves removed over time. We can't rely on the current version
of the governance repository to include the information about who owned
a deliverable, so we need to put that information here in the releases
repository where we can track changes over time.
This patch adds support for a required "team" field to the deliverable
file, using the values set in previous patches in the series, and
updates the rendering code to use it instead of the project list from
the governance repository.
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Change-Id: I5941072c641c05bf0983984cae29a34927246d86
also remove the check that was causing it to skip everything except
liberty
Change-Id: Iceb3fb12916f6e3e31f99014c397d053ecffe892
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add pages to show the work each team has produced. For now, only
official teams using cycle-based release models are included. In a later
phase we will add deliverables that are currently listed as indepdent.
Change-Id: Ieb54aa7a4d2f58f462692e295c8f19978d5baa73
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The ordering in the output file is currently string-ordering, which
puts 1.10.0 before 1.2.0. Use semver ordering to get this in the
right order.
Change-Id: I27291789193b9ff872a56cbefcb8271c8a765127
Add an output option for building the schedule planning calendar
etherpad.
Change-Id: I3be5d94a1cb243a8d9e601b51959a1d97ba93083
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add a script to check deliverables and add release notes links where
needed and available.
Use the script to update the deliverable files for mitaka.
Change-Id: I9b8cd4984532a7d7a1b3689c509e4f7003eb5ca8
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
