...
3d. Announce the creation of the Open edX release branch
For a 2U person to do: Send an email to edx-tech-announce@2u.com explaining that the open-release branch has been created from an edx.org release. Here's an Make a forum post announcing that the branches have been cut and explaining what that means. For example:
Hey everyoneOpen edX developers,
TL;DR: We are now in the pre-release phase for the next Open edX release: Palm. Code merged to master now will not be part of Palm. Keep this in mind as you make changes to master, especially needed fixes: They will need special attention, so reach out.
What is Palm? The next Open edX community release is named Palm. It will be based on the code as of today. We can include your future changes if you alert us to them.
What happened: Today we created the open-release/palm.master branches in our repos. As of now, your day-to-day work is contributing changes you merge to master will contribute to the release after Palm after Palm, which will be called Quince. The community will be stabilizing and testing Palm, and we'll be making fixes on the Palm branches, leading up to the official Palm release in early June.What you should do
What you should do: As you do your workmerge PRs to master, please be aware of fixes that might need to be applied to Palm. I can help get the fix into the release, but you need to let us know there Let the Build-Test-Release Working Group know if there is a fix to be applied. They will need to be cherry-picked to ship as part of Palm, a.k.a. “backported”.
I know this gets confusing, but your code going onto master will now automatically be part of the Quince release (due next December). There is a new Quince wiki page for you to note things that will need to be considered when it comes time to release Quince. Please add features, caveats, and concerns to that page. If you are uncertain whether something should be mentioned there, add it. Or, talk to me the Build-Test-Release WG and we'll figure it out.
What’s next? From now until the Palm release date, the Build-Test-Release group will be actively testing the release branch, finding bugs, triaging them, merging fixes to master, and backporting them to Palm. The Build-Test-Release Testing Coordinator will be kicking off this process soon, and they are happy to take volunteers to find and fix bugs. Keep an eye out if you’re interested. Even if you don’t actively participate, you can help this process by promptly reviewing any bugfix PRs that are made in your repositories.
Have questions? If you want to know more, we have an FAQ about the Open edX community releases. Please reach out if you have any questions.Thanks for all your hard work! You make Open edX software the valued open source platform it is!questions.
--Ned, on behalf of the community Build/Test/Release working group.
3e. Announce upcoming release to the community
Create a topic in the Announcements - Releases category on discuss.openedx.org. ((Add some boilerplate here))
If you created a pre-release branch, you should probably not write a post in “Releases” but in the build/test/release working group category. (see for instance this announcement)
Please notify Please x-post the announcement to the DEPR working group in the #wg-depr-slash-n-burn channel in the Open edX Slack, so that the DEPR working group can help write release notes of deprecated code in accordance with the DEPR Release Notes Process .
...
3e. Get the test process started
Reach out to the Build-Test-Release Testing Manager to make sure they’re kicking off the testing process for the newly cut release.
When they have a test plan ready, add it to Open edX Release Testing.
...
3f. Get the community-supported distribution release process started
Immediately inform the maintainers of community-supported distribution that the upstream release tags have been created and that the distribution release can proceed.
...