| tonyb | I agree on that timing but we know in advance what the tag shgould be so there is no need to use a placeholder tag. We can and should just added the correct tag, albeit non-existent, at the time we create the election. | 04:09 |
|---|---|---|
| tonyb | This *is* the established process, the plaeholder thing happened as a result of human/tooling error | 04:09 |
| tonyb | The point of tagging the governance repo is to be able to see the state of it when the election tooling/roll-generation is run. If we're going to do this placeholder/switcharoo we may aswell just use the actual SHA. | 04:11 |
| tonyb | the tag just makes things nicer: git -C .../governance tag -l | grep election | 04:12 |
| fungi | when i tried it sometime back, i was chided for guessing the next governance tag because "it's semver" and the tc might want to increase a different component of the version string | 12:08 |
| gmann | that is why I am saying guessing the future tag is wrong. one example for that is this error for train electrion. election repo used tag 'feb-2019-elections' which never exit at all | 16:28 |
| gmann | it is better to go with placeholder and when time comes release tag and update in election it takes less than 5 min | 16:29 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!