| opendevreview | Amy Marrich proposed openstack/election master: Adding dates for upcoming election to be displayed on the election page https://review.opendev.org/c/openstack/election/+/886653 | 02:39 |
|---|---|---|
| gmann | yeah | 19:38 |
| gmann | spotz[m]: tonyb let's not put the future tag instead keep the placeholder until tag is actually released | 19:38 |
| spotz[m] | gmann: So which one?:) | 19:42 |
| gmann | I will say to keep 'oct-2023-elections' as placeholder like we did in past elections so that we know that we need to get new tag released and update here. or may be 'todo-oct-2023-elections' is even better so that it is clear that it is a todo | 19:43 |
| gmann | or maybe 'to-be-released' ? | 19:44 |
| spotz[m] | Ok putting it back | 19:44 |
| gmann | whatever you prefer and give clear indication that we need to release new and update here | 19:44 |
| gmann | I like 'to-be-released' | 19:45 |
| spotz[m] | grr, fixing | 19:45 |
| spotz[m] | the script does give the oct one though | 19:45 |
| gmann | yeah, we can modify the script later so that it will be consistent in future | 19:46 |
| opendevreview | Amy Marrich proposed openstack/election master: Adding dates for upcoming election to be displayed on the election page https://review.opendev.org/c/openstack/election/+/886653 | 19:46 |
| tonyb | hmm I thought we fixed the script to generate the semver one. | 20:05 |
| tonyb | gmann: your description of the process is inaccurate. we have always had the unreleased/fictional tag in the configuration. what you describe may be an aspirational process? | 20:11 |
| gmann | tonyb: I did not get. we added a kind of placeholder name for tag in past which is election month naming not the actual tag | 20:23 |
| gmann | governance doing semver tag for many years | 20:24 |
| spotz[m] | I had used what came out of the script, just cut and pasted everything then had to go back and fix some missing spaces | 20:25 |
| gmann | yeah, I think adding a placeholder as 'to-be-released' in script will make it more clear otherwise current tag name which is fictional one can be interpreted as actual tag | 20:26 |
| gmann | tonyb: I did not see any inaccuracy in the mentioned process. I just missed the first step that 'we use the dummy tag name as election month during selecting the election dates' and rest two things are what we have been following for all past elections | 20:30 |
| fungi | right, the old governance tags were the month and year | 20:32 |
| tonyb | gmann: that's my point you're describing the changed process as if it is the current process. I'd you'd said "I think the process should be" or " a new process could be" I would take offence but "the process is" is .... inaccurate | 20:36 |
| tonyb | I'm not going to block the merging of spotz' patch but I am also not going to agree to a process change going forward. | 20:37 |
| gmann | tonyb: not sure what you consider as current, we have been shifted to semver tag in governance since 2018 and election start using those since 2019 election | 20:40 |
| gmann | I think that is what we should consider as current process | 20:41 |
| opendevreview | Ghanshyam proposed openstack/election master: Fix the tag to be used for setting election config https://review.opendev.org/c/openstack/election/+/886787 | 20:41 |
| gmann | updating the script to give clear indication on tag things ^^ | 20:41 |
| gmann | one good example of this tag error is we used 'feb-2019-elections' in train election which does not exist. as governance shifted to semver tag since 2018. from ussuri election we moved election config to use the semver tag | 20:47 |
| gmann | after ussuri election we followed the process i described 1. add dummy tag in election config (election month tag) 2. on election_deadline, release new tag of governance repo 3. update the released tag (server) in election config | 20:48 |
| gmann | * 2. s/election_deadline/email_deadline | 20:48 |
| fungi | for the avoidance of doubt, this is what the git history of the election repo says the sequence of tag field values in configuration.yaml has been over time: https://paste.opendev.org/show/bq11pXBBiqxcop9JhQCw/ | 21:01 |
| * fungi has no actual opinion on what the process for placeholder values should be, just providing data | 21:03 | |
| fungi | fwiw, over the last few elections i had no idea those were being used as placeholders, i thought they were just mistakes from the config generation script never getting corrected when we switched to semver-style tags in governance | 21:04 |
| gmann | yes, since ussuir we have been updating the actual tag later on election config so script generated election-month tag name were used as placeholder tag only which get updated to correct one once we actually release those for governance | 21:09 |
| gmann | 886787 make the placeholder name clear that they are not actual tag | 21:09 |
| opendevreview | Ghanshyam proposed openstack/election master: Fix the tag to be used for setting election config https://review.opendev.org/c/openstack/election/+/886787 | 21:40 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!