Stream: fmg
Topic: Branches
Grahame Grieve (Dec 22 2019 at 21:55):
Some of the requests for ballot publication are from github branches. Does anyone think that this is an issue?
(at least one is because the STU1 is the trunk, and it's not published, and so the ballot is in a branch...)
Lloyd McKenzie (Dec 22 2019 at 21:59):
Why are they going to ballot before they've even published STU? Isn't the idea that we're supposed to get implementation feedback first?
Lynn Laakso (Dec 22 2019 at 22:00):
publication has been approved but not yet accomplished, I think
Lloyd McKenzie (Dec 22 2019 at 22:02):
Even still, there ought to be at least 6 months between publication and going to ballot again in normal circumstances. So the question would be "what's the special case for this ballot?"
Lynn Laakso (Dec 22 2019 at 22:03):
STU1 is FHIR R3, ballot is FHIR R4
Lloyd McKenzie (Dec 22 2019 at 22:53):
I guess that qualifies :)
Lloyd McKenzie (Dec 22 2019 at 22:54):
Why are the others posting from branches Grahame?
Grahame Grieve (Dec 22 2019 at 23:08):
I don't know. @Lynn Laakso which ones?
Lynn Laakso (Dec 22 2019 at 23:09):
deqm and cqf-measures
Josh Mandel (Dec 23 2019 at 16:14):
For ballot, I don't think it should matter where the source is (assuming it's in an appropriate HL7 repo). Ideally we'd enforce freezing ballot content by making the build framework support commit- or tag-addressed builds.
Josh Mandel (Dec 23 2019 at 16:14):
That said: currently if content is a build.fhir.org in a branch, it'll auto-delete that branch after a certain amount of time.
Josh Mandel (Dec 23 2019 at 16:14):
So branches are unsuitable for ballot hosting unless the IG author is aware and triggering periodic builds during the ballot timeframe.
Grahame Grieve (Dec 23 2019 at 19:31):
we do not ballot off build.fhir.org
Josh Mandel (Dec 23 2019 at 22:36):
Great. So I'm not clear on why it matters whether the source is in a branch.
Lloyd McKenzie (Dec 23 2019 at 23:46):
I think the primary concern is that whatever passes ballot needs to be the basis for future change. Generally that means it should be the main branch.
Last updated: Apr 12 2022 at 19:14 UTC
