Stream: IG creation
Topic: CI Build and display of versions in header and footer
Eric Haas (Sep 08 2020 at 17:36):
Unless I missed memo I think we should have an established convention to use version = 'current' for the CI Build, because I don't think we should have versions in the current (CI) builds. They are often ( in my case ) leftover from the prior publication cycle until we decide on the next version. I forget to refresh the CI build then the version shows up in the title, pub box and footer where is pointing the wrong package "n.n.n" instead of "current". What do other authors do?
Lloyd McKenzie (Sep 08 2020 at 18:09):
I try to remember to increment - like we do with FHIR core, but I probably actually do so only half the time. Though really, the issue is remembering to change the version at all - whether to 'current' or to the next number increment, the real issue is leaving the version unchanged and having two distinct specs claiming to be the 'ballot' version number or the 'formal publication' version number
Grahame Grieve (Sep 08 2020 at 21:27):
it's a good idea to do something about this, but not that. I'll work on this as part of the build process I'm working on
Last updated: Apr 12 2022 at 19:14 UTC
