Stream: IG creation
Topic: Template release
Grahame Grieve (Sep 21 2020 at 10:00):
@Lloyd McKenzie @Jose Costa Teixeira @Eric Haas I want to do a new release on the base template. Which means a new release on all the dependent templates. Where are we with this?
Jose Costa Teixeira (Sep 21 2020 at 10:05):
Not far, I think.
HL7 templates and IHE templates have
"dependencies": {
"fhir.base.template": "current"
}
we can decide whether these templates depend on the current or a fixed version (i guess stick to a known version is safer, but at this moment there's no big impact, we can do that after the base template release)
Grahame Grieve (Sep 21 2020 at 10:06):
the current versions all depend on current
. I will fix that to the latest when I do a release (happens automatically)
Jose Costa Teixeira (Sep 21 2020 at 10:51):
Are there any must-have changes to base template? I don't see anything that seems critical from the issues
https://github.com/HL7/ig-template-base/issues?page=2&q=is%3Aissue+is%3Aopen
Lloyd McKenzie (Sep 21 2020 at 13:05):
Doing a release is fine
Jose Costa Teixeira (Sep 21 2020 at 14:18):
we should then accounce to every template author that uses the base template.
Which gives the idea: should we give template authors some mechanism to see whether their template is based on the latest"?
Grahame Grieve (Sep 21 2020 at 15:36):
I don't know what 'based on latest' means
Jose Costa Teixeira (Sep 21 2020 at 15:40):
Soon we'll have a v1.0 which is current. Other templates will be either based on 1.0 or "current".
After that, we will fix a bug in v1.1 And in a few months when we have a v2.0. For those based on 1.0 or based on "current", do we let them know that their template is based on a v1 and should be based on a v2? or we always ask them to use current?
Grahame Grieve (Sep 21 2020 at 15:43):
again, I don't really know what you mean. "Current" templates are always based on "Current". Released templates with versions are always based on released versions
Jose Costa Teixeira (Sep 21 2020 at 17:12):
IHE#current template is based on base#current.
Once we release base#1.0.0 now, and then base#1.1.0 later, does IHE#current need to be based on base#current?
Grahame Grieve (Sep 21 2020 at 17:23):
umm. current is always based on current. I will automatically release a new fixed version of the IHE template when I release new version of base
Jose Costa Teixeira (Sep 21 2020 at 17:48):
ok then this means we need to issue releases of all templates?
Grahame Grieve (Sep 21 2020 at 17:50):
I will do that, yes, for all the templates I know about
Jose Costa Teixeira (Sep 21 2020 at 17:54):
We should be taking that work, or at least part of it as much as possible.
Let me use the Belgian template as example - what is there to do ? Update package-list?
Grahame Grieve (Sep 21 2020 at 18:01):
I don't know about the Belgian template. But in principle, the work is:
- maintain a change list somewhere.
- high light the changes in package-list.json under the next version
- when my code that does the release creates a new release, it will pick up the nexts version entry, finish it, and then do the release
Jose Costa Teixeira (Sep 21 2020 at 18:07):
I got at least a bit of that, so that's ok for now.
Last updated: Apr 12 2022 at 19:14 UTC