In the situation that a candidate has registered an email address with
the Foundation and that address is a secondary address in gerrit we'll
fail to fin any validating changes.
So fix that by finding an account that matches the email address under
review and use that gerrit account for looking for change owners.
Change-Id: I588463e5527c4ebfd24dc8f0d94d56d18f5d5673
This change moves parameter from utils.py and index.rst to the
configuration.yaml. Moreover this change does:
* Use ISO 8601 dateformat in configuration
* Change events extension to use datetime instead of calendar
* Add a configuration extension to render doc substitutions
Change-Id: Ie35cb9ae2c334814afaa36b3afd606c8bcf62616
./doc/source/_exts/candidates.py:20:1: H306 imports not in alphabetical order (jinja2.filesystemloader, jinja2.environment.environment)
./doc/source/_exts/events.py:17:1: H306 imports not in alphabetical order (os, calendar)
./doc/source/_exts/events.py:21:1: H306 imports not in alphabetical order (jinja2.filesystemloader, jinja2.environment.environment)
./openstack_election/check_candidacy.py:62:29: E126 continuation line over-indented for hanging indent
./openstack_election/utils.py:27:1: H306 imports not in alphabetical order (yaml, re)
./openstack_election/cmds/close_election.py:90:9: H232 Python 3.x incompatible octal 755 should be written as 0o755
./openstack_election/tests/test_utils.py:25:21: E126 continuation line over-indented for hanging indent
./tools/new-election.py:18:31: H301 one import per line
./tools/new-election.py:27:5: H233 Python 3.x incompatible use of print operator
./tools/new-election.py:31:5: H233 Python 3.x incompatible use of print operator
./tools/new-election.py:41:5: H233 Python 3.x incompatible use of print operator
Co-Authored-By: Nguyen Hung Phuong <phuongnh@vn.fujitsu.com>
Change-Id: Idd9bc1f1f92da1658e6da2af588c575ee0ba2cb0
This change improves candidate list rendering using gerrit to retrieve fullname.
The list rendering now uses the openstack_election libraries and some part
have been refactored accordingly.
Change-Id: Iccba3e4c529740758323b51548a2144fc7c77879
There seems to be an issue when pasting full review link with ChangeId so let's
use cgit instead. Moreover it's more simple and lightweight to check like that.
Change-Id: Ic14f9edbd25bb56f17798c365b2e636d1a8fd452
There are a couple of problems with the way Stable branch maintenance is
validated:
1. Any change in any repo, regardless of branch is accepted
2. The the key name is incorrect. (it's 'maintenance' not 'Maintenance')
Correct the key name, and given it needs to specify the branch make it
specific to Stable branch maintenance.
Change-Id: I5d7bb4eab433766c2848c77f7cc4e1f502c0c97c
Currently the code in this repo is half modular have series of scripts.
Migrate the code to be more modular. The main benefit to this is
testing is easier.
Testing is added in a followup patch
Change-Id: Ic1262436147ecdb818ee259e2e85fca8df09d722