About hapifhir release process and how to handle forked projects
11 views
Skip to first unread message
Dong Wang
Jun 4, 2025, 5:18:32 AM6/4/25
to HAPI FHIR
Also posted on github:
Shouldn't the further commits in release branches always merged back to master? By doing this, it would be much easier and cleaner for the running hapi service version upgrade (eg. 8.0->8.2). As those changes that's not in 8.0 will be included and resolved in 8.2.
The release process is outdated: https://github.com/hapifhir/hapi-fhir/wiki/Release-Process
Description:
I noticed that each release branch has further changes that's never merged back into master. Some of those are hot fixes.
eg:
https://github.com/hapifhir/hapi-fhir/compare/master...rel_8_0_mb
I noticed that each release branch has further changes that's never merged back into master. Some of those are hot fixes.
eg:
https://github.com/hapifhir/hapi-fhir/compare/master...rel_8_0_mb
Shouldn't the further commits in release branches always merged back to master? By doing this, it would be much easier and cleaner for the running hapi service version upgrade (eg. 8.0->8.2). As those changes that's not in 8.0 will be included and resolved in 8.2.
The challenge out team is facing, is to find a proper way to fork the project, make customized updates, and keep that in sync with ongoing hapifhir master updates.
Is anyone facing the same challenges? How is your team handling the release/version upgrade?
Reply all
Reply to author
Forward
0 new messages