ecbdd0dbb9
Most of the election tooling work on seperate events of PTL and TC election. If election is combined then setup_election_config generate the combined event( for example 'TC & PTL Election') and it does not work with those tools/scripts. This fixes it and even for combined election it generates the separate events. If we look at the election site, the separate events are more clear for users. Generated config looks like below: Change-Id: I7d2e540dea9d89c832f6d9e3e9da743fe8d39295 --- release: 2023.2 election_type: combined tag: mar-2023-elections tc_seats: 4 timeframe: name: Zed-2023.1 start: 2022-03-11T00:00 end: 2023-02-15T00:00 email_deadline: 2023-02-15T00:00 timeline: - name: TC Nominations start: 2023-02-01T23:45 end: 2023-02-15T23:45 - name: PTL Nominations start: 2023-02-01T23:45 end: 2023-02-15T23:45 - name: TC Campaigning start: 2023-02-15T23:45 end: 2023-02-22T23:45 - name: TC Election start: 2023-02-22T23:45 end: 2023-03-08T23:45 - name: PTL Election start: 2023-02-22T23:45 end: 2023-03-08T23:45 Change-Id: I5b1766d0fce9eb7ded000a7b582a8e4086314831 |
||
---|---|---|
.. | ||
__init__.py | ||
change_owners.py | ||
check_all_candidacies.py | ||
check_candidacy.py | ||
check_manual.py | ||
ci_check_all_candidate_files.py | ||
close_election.py | ||
create_directories.py | ||
generate_rolls.py | ||
render_statistics.py | ||
search_rolls.py | ||
setup_election_config.py | ||
template_emails.py | ||
update_governance.py |