| fungi | spotz_: looks like it's generated during the doc build using a custom sphinx extension | 13:01 |
|---|---|---|
| fungi | https://opendev.org/openstack/election/src/commit/35c2bc9/doc/source/_exts/events.py#L28 | 13:02 |
| fungi | found via `git grep 'events\.rst'` in the repository | 13:03 |
| fungi | skimming that extension, it uses a jinja2 template and fills in values from the timeline section of the supplied config | 13:04 |
| spotz_ | I wonder why a find . -name couldn't fine it | 13:21 |
| spotz_ | Ok here's the issue, knikolla wants the dates updates to give folks a heads up but we don't have a name yet. Are we doing the directories as numbers? | 13:22 |
| spotz_ | I figured that was the best page to do it, but I wasn't sure we wanted the configuration.yaml commited yet | 13:24 |
| fungi | find was looking for files named events.rst, not references to it inside other files | 13:28 |
| fungi | that file won't exist until you generate the docs (tox -e docs) | 13:28 |
| fungi | looks like last election cycle used the name "bobcat" in configuration.yaml and for the subdirectory under candidates/ | 13:30 |
| spotz_ | Yeah but C doesn't have a name yet | 13:47 |
| fungi | right, i mean, you can try to do it as 2024.1 or you can use a placeholder like just the letter c | 14:01 |
| spotz_ | I did use 2024.1 to generate the dates locally. So we at least know that part of elections work with numbers | 14:02 |
| fungi | if we're going to run into problems, it will likely be around sorting | 14:13 |
| spotz_ | Should I rerun as c? Then we can delete the c stuff later and replace with the name? | 14:22 |
| fungi | i think that happened with antelope and bobcat | 14:32 |
| fungi | you can probably find it if you `git log -p configuration.yaml` | 14:33 |
| fungi | looks like for the 2023.1 cycle we started out with antelope and stuck with that, for 2023.2 cycle it started with "bugbear" as a placeholder and was later updated to 2023.2 and then (due to some unspecified problem) was switched to bobcat at the start of the election | 14:35 |
| fungi | tonyb's name is on that last patch from 4 months ago, so maybe he remembers what the problem was without me needing to go hunting in the irc channel logs | 14:36 |
| spotz[m] | Ok I’ll do it as C and we can change it later | 15:29 |
| fungi | this far ahead, it probably can't hurt to start it as 2024.1 and then see if we can work out why 2023.2 broke last time and try to fix it before it becomes a problem | 15:58 |
| spotz_ | Ok so I'll build and then commit what's on my machine and put it up | 16:31 |
| 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 | 17:22 |
| 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 | 17:42 |
| tonyb | There was linkage between the release tooling and election tooling with the series name being the only thing that was in common. | 21:06 |
| tonyb | Since then the tools have been updated to handle release-ids so 2024.1 should be totally fine. | 21:07 |
| tonyb | FWIW I have it on my list for next week to tackle the essential parts of https://etherpad.opendev.org/p/TC_PTL_Elections2023.2Bobcat#L91 | 21:08 |
| fungi | cool, thanks for confirming! sounds like everything's probably set | 21:19 |
| tonyb | Yup should be good to go. | 22:21 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!