-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 4.10.0 #9216
Labels
Type: Internal process
An organizational process, eg: doing a release
Milestone
Comments
5 tasks
The upgrade of the demo instance to the 4.10.0 release not working. Ticket has been raised here. However, creating an EKS instance of version 4.4.1 and 4.9.0 and upgrading them to 4.10.0 works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Planning - Product Manager
Development - Release Engineer
When development is ready to begin one of the engineers should be nominated as a Release Engineer. They will be responsible for making sure the following tasks are completed though not necessarily completing them.
<issue>-update-version
branch (eg:1234-update-version
) and set the version number in thepackage.json
andpackage-lock.json
. The easiest way to do this is to usenpm --no-git-tag-version version <major|minor>
. Once the version is updated, submit a PR tomaster
branch.master
since the last release are closed and mapped to the milestone.Releasing - Release Engineer
Once the PR has been merged into
master
, and themaster
branch has the new version number, then the release process can start:master
named<major>.<minor>.x
incht-core
. Post a message to #development Slack channel using this template:<major>.<minor>.<patch>-beta.1
by creating a lightweight git tag (e.g.git tag <major>.<minor>.<patch>-beta.1
) and then push the created tag..json
file tocht-core/tests/scalability/previous_results
. More info in the scalability documentation.Release Notes
section to the new release page.<major>.<minor>.<patch>
. In the releases tab, you select the "Choose a tag", type tag in the search box, then create a tag for the release<major>.<minor>.<patch>
. Next, change the Target dropdown to the release branch (eg:4.4.x
). Ensure the release notes PR above is merged. Add a link to the release notes in the description of the release.id: medic:medic:<major>.<minor>.<patch>
/config/demo
folder to thedemo-cht.dev
server.is:issue label:"Affects: 4.x.x"
, replace4.x.x
with the previous version number. Add any open "known issues" from the prior release that were not fixed in this release. Done by adding the correctAffects: 4.x.x
label.The text was updated successfully, but these errors were encountered: