Stream: implementers
Topic: List of breaking changes?
Sean McIlvenna (Feb 21 2018 at 23:14):
Hi, is there somewhere on build.fhir.org that has a running list of breaking changes?
Lloyd McKenzie (Feb 21 2018 at 23:34):
Nope. We compile that list during the QA period prior to formal balloting and publication. It's too much work to maintain otherwise (with changes being made, tweaked, reversed, etc.). If you want to get a sense of changes, you can look at gForge and filter to the non-compatible applied changes.
Sean McIlvenna (Feb 21 2018 at 23:46):
Yah.. figured gForge was the goto place. Thought I'd ask, though.
Lloyd McKenzie (Feb 22 2018 at 01:04):
If someone wants to go through gForge and compile the list when we go to ballot, I'm quite sure Grahame wouldn't fight them for the privilege... :) Turning tracker items into summary form that conveys the important gist without overwhelming with detail isn't easy.
Jose Costa Teixeira (Feb 22 2018 at 05:35):
something I did a few years back in my toolset:
For requirements / Changes that were "critical"/"customer facing", the field "Release note summary" had to be filled in. This was then poured onto the Release Notes.
Jose Costa Teixeira (Feb 22 2018 at 05:35):
Perhaps would be possible/interesting to enforce this in our change tracker toolset?
I worked with Requirements, not Change requests, but the idea should apply in the same way.
Lloyd McKenzie (Feb 22 2018 at 05:51):
An enhancement to consider for JIRA once we're there perhaps :)
Grahame Grieve (Feb 22 2018 at 06:17):
it get's overwhelming very quickly. It's not good giving you a change list that's 500-800 items long. No one can find anything. That's why we've focused more recently on giving good diff views. @Sean McIlvenna have you found them? there's 2: R3/R2 difference (which I'll update during QA period) and page difference
Sean McIlvenna (Feb 22 2018 at 14:47):
I'm not sure where the R3/R2 differences are... I found the page differences.
I'm more-so looking for a list of changes that I should be aware of if I'm trying to target the current build. Hard for me to know what I need to change in a system without searching through all gForge tickets.
Lloyd McKenzie (Feb 22 2018 at 16:16):
We don't (and can't) reasonably maintain that list for the current build. (And it could change 30 seconds after you looked at it anyhow.)
Peter Jordan (Feb 22 2018 at 19:45):
It might be worth asking the Toolsmiths - particularly those who produce the reference libraries. From a developer's perspective, the IDE lists everything I need to change when I migrate to a new version of the C# Reference Library.
Brian Postlethwaite (Mar 04 2018 at 21:34):
That's not the complete list in the dotnet ib, but it is the ones that I've personally had to deal with...
Last updated: Apr 12 2022 at 19:14 UTC
