Mistral, Oslo, Requirements and Release Team are DPL projects so we
shouldn't include them in the election.
$ grep -B1 ': distributed' ../governance/reference/projects.yaml
mistral:
leadership_type: distributed
--
oslo:
leadership_type: distributed
--
Release Management:
leadership_type: distributed
--
requirements:
leadership_type: distributed
$
Change-Id: I59764adf53d96611c482c2ba6a5a1e14f73155c2
Fixes:
[pbr] Generating ChangeLog
.../lib/python3.11/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
.../lib/python3.11/site-packages/setuptools/dist.py:770: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
warnings.warn(
.../lib/python3.11/site-packages/setuptools/dist.py:770: UserWarning: Usage of dash-separated 'author-email' will not be supported in future versions. Please use the underscore name 'author_email' instead
warnings.warn(
.../lib/python3.11/site-packages/setuptools/dist.py:770: UserWarning: Usage of dash-separated 'home-page' will not be supported in future versions. Please use the underscore name 'home_page' instead
warnings.warn(
running editable_wheel
Change-Id: I248d6a305108f4eb49b8ce10829fb4f650104c8a
Currently the event name is limited to 'x-final', this doesn't
work for current releases. Update that to determine the correct
tag.
Change-Id: I14a2d71a0bc26c837ebe4dfebbcfc9b05f02b069
If the release name passed into the tool doesn't yet have a schedule,
which is actually the most common use case, we won't be able to
auto-detect a date. In that case let's bail somewhat nicely.
Change-Id: I4072e73c15d0299755fcce43f8b35798179719c3
Setting a variable to itself should be a no-op right? Frankly I have
no idea why I did this so remove it.
Change-Id: I9f9851c76455e5d559ba68921dfd29557a64b574
For now the release *must* be the name, not the "version". Fixing this is a slightly bigger issue.
Change-Id: I3a4ad7089e7a58b30f25ce05823fdbe34cef3550
Tuesday was selected because it was early in the week and was "safe"
for APAC and US timezones. Releases actually happen on Wednesdays
so for something more like consistency lets do make elections also
happen on Wednesdays
Change-Id: If66602b12eb77b17904427149ab81ce7a21d9492
tox.ini started failing with Tox4 which had some
incompatible changes. One of the reason for failure
is due to the skipsdist = True with usedevelop and it
seems it was never supported.
Change-Id: If70b1a8b17bd925b04b35366ff80fd5dacf19c3c
governance repo tags and release names are place holders until
those details are settled.
Setting combined Election
Release is at: 2023-03-24
Latest possible completion is at: 2023-03-10
Moving back to Wednesday: 2023-03-08
TC & PTL Voting from 2023-02-22T23:45 to 2023-03-08T23:45
TC Campaigning from 2023-02-15T23:45 to 2023-02-22T23:45
TC & PTL Nominations from 2023-02-01T23:45 to 2023-02-15T23:45
Set email_deadline to 2023-02-15T00:00
Setting TC timeframe end to email_deadline
Begining of Zed Cycle @ 2022-03-11 00:00:00+00:00
End of Antelope cycle @ 2023-02-15 00:00:00+00:00
Election timeframe: 341 days, 0:00:00s
[1] Affectionately call bugbear, until the OIF selects a name
Change-Id: Ic9bc45fcb7dbc9faa48a1384f441fd8eb49ba46c
The list of officals has grown overtime, but not everyone is active,
nor due to personal/employment chnages, can actully perform this role.
Remove officials for now except official(s) who commented on the review
and expect/required to opt-in affrim they're available.
Change-Id: I9f718f2eeae4aaf194fa8e2f7caa0d976182e6c8
It is no longer supported by jammy and lead us to the following errors with the announce-release job.
```
No package matching 'python-dev' is available
```
Change-Id: I2a1c4c2fc169a2eec87fee87e584661798d90afa
Adding the policy statement to combined election which was already
added in PTL and TC election voting kickoff templates
Change-Id: I10fbbab9d11512cb66a3e3eaaa3cfd4159e48513
In previous patch file was mistakenly placed into wrong cycle
overwriting previous one. Restore zed cycle content and put properly
antelope candidacy.
Change-Id: I3b02c2f9cc80868040dfcb36a4870fd33f0c43a4
In order to give folks time to opt-in as well as to assure the CIVS
system is ready we are adding a seperate` TC campaign back in until 9/12
Change-Id: Idedf339fecb5f83e0a3e2383145c1885c8308875
Let's exactly match tag version which number is managed
on openstack/releases repository.
Depends-On: Ie3f763c2012930e6b14ac69d0667ba1372892b29
Change-Id: I92a7432978c6e30eb637806a772421cd1b476b51
