Stream: fmg
Topic: R4 publication
Grahame Grieve (Oct 30 2018 at 23:04):
Also to take up in the next few weeks - are there any resources in the currnent build that we won't publish as part of R4?
Lloyd McKenzie (Oct 31 2018 at 02:32):
And are there any unapproved resources we want to approve and allow them to move from FMM0 to FMM 1 or 2
Grahame Grieve (Oct 31 2018 at 03:04):
http://build.fhir.org/fmg.html - we need to review that tomorrow
Grahame Grieve (Nov 01 2018 at 03:03):
I'm not sure what to call this fork version of FHIR that I'm working on for the redo of the normative ballot
Grahame Grieve (Nov 01 2018 at 03:03):
updates for forked versions would usually be an increment in the patch, so it would be 3.5.1
Grahame Grieve (Nov 01 2018 at 03:04):
but it has real changes in it - that means it would be 3.6.0 - but the trunk is presently 3.0
Grahame Grieve (Nov 01 2018 at 03:05):
if I was pulling the ballot version of trunk, it would be 3.7.0 and the trunk would become 3.8.0
Grahame Grieve (Nov 01 2018 at 03:06):
this version isn't 'real' = we're never going to support it, it's not going to have implementation collateral (e.g. no NPM package)
Josh Mandel (Nov 01 2018 at 03:11):
Does it need a number in our sequence? If so, I guess just one we'll skip over.
Grahame Grieve (Nov 01 2018 at 03:11):
no I can make anything we want up....
Grahame Grieve (Nov 01 2018 at 03:11):
specially since it's not a real version
Grahame Grieve (Nov 01 2018 at 03:11):
3.6a.0
Lloyd McKenzie (Nov 01 2018 at 03:12):
I was going to suggest something like that. Or even 3.5a.0
Grahame Grieve (Nov 01 2018 at 03:14):
oh that's what I meant
Josh Mandel (Nov 01 2018 at 03:45):
Might even use a descriptive term (3.5-reballot or suchlike)
John Moehrke (Nov 01 2018 at 12:40):
is there a reason to conserve numbers? I am not clear on why you don't just follow the numbering plan. Yes it will be a short lived, but that sometimes happens in all projects. (although I do like Lloyd's uniquely Canadian approach to the problem... eh?)
Grahame Grieve (Nov 01 2018 at 20:29):
I am uploading to http://hl7.org/fhir/2018Dec
Grahame Grieve (Nov 01 2018 at 20:29):
probably take 3-4 hours
Grahame Grieve (Nov 01 2018 at 20:50):
is there a reason to conserve numbers?
it takes me approximately a day to change version numbers in the trunk - there's more and more cascading effects
Grahame Grieve (Nov 02 2018 at 01:01):
ok done and open for review - see http://hl7.org/fhir/2018Dec/
Lloyd McKenzie (Nov 02 2018 at 02:26):
I'd be more assertive:
FOR THIS BALLOT: Only comments related to changed items will be considered. ALL OTHER FEEDBACK WILL BE MARKED AS "NOT RELATED" AND NOT CONSIDERED IN ANY OTHER WAY. Feedback on other portions of the specification may be posted to the [gForge tracker] for consideration as part of the R5 release.
Lloyd McKenzie (Nov 02 2018 at 02:27):
For the Terminology/Conformance ballot, ONLY the following 3 changes are open for comment:
Lloyd McKenzie (Nov 02 2018 at 02:28):
Add 'ONLY' for infrastructure too. And end with:
The above changes are the ONLY areas of the specification subject to comment in this ballot.
Lloyd McKenzie (Nov 02 2018 at 02:35):
Transparancy is either not working or not noticable on the other pages
Grahame Grieve (Nov 06 2018 at 05:01):
updated
Last updated: Apr 12 2022 at 19:14 UTC
