FHIR Chat · R4A Editorial Process · committers

Stream: committers

Topic: R4A Editorial Process


view this post on Zulip Grahame Grieve (Jun 03 2020 at 22:57):

Place holder for discussion

view this post on Zulip Grahame Grieve (Jun 03 2020 at 23:09):

see https://chat.fhir.org/#narrow/stream/179240-Announcements/topic/Release.20R4A. FMG is considering what the editorial policy for a release like this would be.

there's a draft page here for editorial rules here: (@Lloyd McKenzie please provide link)

One question that arises is: Do we have an approval processes for PRs to release 4A prospectively (and who should do it?), or just review it retrospectively? Should it be branch in the main repo, or it's own repository?

@Josh Mandel can we protect a different branch from master with different approval rules?

view this post on Zulip Josh Mandel (Jun 03 2020 at 23:11):

Yes we should be able to configure distinct protection rules for a different branches.

view this post on Zulip Grahame Grieve (Jun 03 2020 at 23:12):

then we have to figure out if we want to

view this post on Zulip Lloyd McKenzie (Jun 03 2020 at 23:13):

https://confluence.hl7.org/display/FMG/Proposed+guidance+for+R4A+Scope

view this post on Zulip Lloyd McKenzie (Jun 03 2020 at 23:14):

Note: the 4A moniker is because 4.1 creates some challenges with current versioning processes. Formal naming of the release will be discussed later


Last updated: Apr 12 2022 at 19:14 UTC