list-deliverables is already able to focus on a series. Add a new option
to let it show only items that do not have a stable branch for that
series. This can take the place of some of the tracking we were doing on
the old dashboard.
Change-Id: I57a51b5de9cd289369330a42dbf15003bedac091
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This new command will replace the one in the release-tools
repository. It uses the deliverable data for a series to produce a
dashboard for tracking the cycle-with-milestone releases so we can set
up a spreadsheet to collaborate on keeping track of those releases.
The old command included deliverables using other release models, but
those are less important/useful to track in this manner.
Change-Id: Ic613d65ae3d143cc910fec201205f1f84fde761c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
When we query for all deliverables in a series without specifying a
team, the team value returned is None. When that's passed to
Deliverable(), we don't know who the real team is. Look it up in the
parsed data instead of reporting None.
Change-Id: Ifef19450b5393dbd3f0aedb500b7d3c06aa749d0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This configuration makes it easier to work on changes to the tools.
Change-Id: Ic4afe2a811d6eb2163a2590a865b0f56d1474eb8
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Somehow an earlier commit removed a lot of the indentation that made the
README actual readable. Restore it.
Change-Id: I53e9400c42bfd5f6d23250821b6821ce2c9c7148
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
If we can't connect to the launchpad API, emit a warning but continue. 99%
of the time we don't need to check the launchpad name anyway, so failing
because LP is down is just frustrating and not useful to anyone.
Change-Id: I21b1b910894645ea1743c36bc1d92130cc92129e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Early on when we only had a few deliverable files it was safe to apply
validation changes to all of the current release series. Now that is no
longer the case, because doing so takes far too much time and the jobs
fail regularly when there are so many repos to check.
We have unit tests for the validation rules now, so it is safer to make
changes. This commit changes the default behavior so that if the commit
under review has no deliverable files changed the validate job does
nothing.
Change-Id: I3ab4b71fb245661579cc528526b42f592ef32f7f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is the first newton release for this project.
Create stable/newton branch from the commit hash.
Change-Id: I993769d38862157497b93e34bfdac455cf508a51
Some important bug fixes were added since 1.0.0 release.
So we hope to make a new release for python-senlinclient.
Change-Id: I73718bd7ae4cd5d6a3b722e5a6a325cbd8f1a8cf
A recent change landed in openstack-dev/hacking [1]
adding an option to pass in the local check factory via
CLI. We need this change for some dependant work [2]
and therefore I'm proposing a new minor release.
NOTE:
- The hacking change [1] only applies when using the new
CLI option.
- No new hacking checks are introduced since the last release
of hacking (0.12.0). See [3] for a branch compare.
- I've tested openstack-dev/hacking master branch with neutron
pep8 from master to ensure no regressions were introduced.
[1] https://review.openstack.org/397940/
[2] https://review.openstack.org/350723/
[3] https://github.com/openstack-dev/hacking/compare/0.12.0...master
Change-Id: Ibd88217ad30460aba77df287724ead156e9e45c4
If the SHA doesn't exist, there is no point in running extra
ancestry / branch match checks and report extra errors which
are just consequences of the blatant original error.
Change-Id: I945a8de371795ee085bb31bde7360111fc81e257
For the first tag in the series, we skipped the descendant
check, which means that an existing SHA from a wrong branch
would pass checks. This change adds a branch match check to
cover that specific case and emit an error.
This change removes a warning which was emitted for first
releases, so we adjust the expected warning counts for some
impacted tests.
Change-Id: I741449a11ea68caeadd5be4aef8d0130efb5f5ec
Now that branches can be created on demand, update the process document
to replace the manual instructions with reminders and review
instructions.
Change-Id: I1d8ef79281b937543d9dbf22bf97d7593301f0e9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Propose a patch with branch instructions for the release-test repo to
verify that the job for creating the branches works properly.
Change-Id: I57e383e7aac03826e0865c7bdf55a81410407bef
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
