Release/26.07.16

[perrymanmd]

First cut of script to update release/26_02_17 to release/26_07_16

[MikeNeilson]

Marking as request changes so it doesn't get merged to main.

branches are deleted on merge (though release/*) should be protected.

If these changes should be merged into main, a separate branch specific to that action should be created.

However, it is likely best we do that after we have confirmed all of the schema update operations.

[perrymanmd]

Marking as request changes so it doesn't get merged to main.

branches are deleted on merge (though release/*) should be protected.

If these changes should be merged into main, a separate branch specific to that action should be created.

However, it is likely best we do that after we have confirmed all of the schema update operations.

Okay - I just made the PR because that the update script and dependencies should be available for future branches off main.

[MikeNeilson]

Okay - I just made the PR because that the update script and dependencies should be available for future branches off main.

Correct, but after they are verified.

The process is

1. Create the release branch
2. Get the initial update scripts setup
3. Tag the first RC
4. ... profit? no, more likely find issues that need to be fixed and by doing so before merge into main, less commits overall to main.

I will note there's also a few PRs like #201 that need to be reviewed and merged to main then 26.07.16 before final release.

That reason we don't do the update main with the release work directly from the release branch is also because they are allowed to diverge, we don't stop work on main and some similar files may be affected.