Git checkout release/teak.master

Open edX developers! We just created the release/teak.master branch in 34 Open edX repositories. :warning: THESE BRANCHES ARE NOT FOR PUBLIC CONSUMPTION :warning: They are only meant to provide a first reference point for developers and contributors, notably the Build/Test/Release working group, who want to help build Teak, the next release of Open edX.

Please report any issues that you find by opening an issue on the Build/Test/Release Working Group board.

For reference, here is the full list of repos that are included in the release:

openedx/cs_comments_service
openedx/xqueue
openedx/openedx-demo-course
openedx/course-discovery
openedx/credentials
openedx/frontend-app-gradebook
openedx/frontend-app-publisher
openedx/frontend-app-profile
openedx/frontend-app-account
openedx/frontend-app-learning
openedx/enterprise-catalog
openedx/frontend-app-support-tools
openedx/license-manager
openedx/frontend-app-authoring
openedx/frontend-app-discussions
openedx/frontend-app-authn
openedx/frontend-app-learner-record
openedx/frontend-app-ora-grading
openedx/frontend-app-communications
openedx/enterprise-access
openedx/docs.openedx.org
openedx/frontend-app-learner-dashboard
openedx/xblock-skill-tagging
openedx/event-bus-redis
openedx/frontend-app-ora
openedx/frontend-plugin-framework
openedx/edx-platform
openedx/edx-notes-api
openedx/cypress-e2e-tests
openedx/openedx-translations
openedx/openedx-app-android
openedx/openedx-app-ios
openedx/aspects-dbt
openedx/platform-plugin-aspects
4 Likes

@farhaanbukhsh - from what I can see the branches are named just release/teak.master?

yes @sarina it was decided in Should we rename the release branches? - #12 by kmccormick, that the coming release should have release instead of open-release. It was planned for Sumac but ended up doing that in Teak.

Great. I edited the title of your post to reflect that.

oops! thank you so much @sarina :slight_smile:

:thinking: Didn’t we agree to name the branches release/teak and not release/teak.master? What’s the use of the “.master” suffix? :eyes: @kmccormick

@regis I think I made a goof up here, I was not able to understand it, I thought the only change was open-release to release.

It’s OK. Can we rename the branches?

I haven’t been involved in this in a while, but yes, we did discuss release/<tree> as the new branch format and release/<tree>.<number> as the new tag format. If it’s possible to rename the branches then I think that would be good idea.

@kmccormick @regis I think we can do this, I am planning for sumac.3 I will take the opportunity to rename the branch as well.

2 Likes

@farhaanbukhsh any update on the branch renaming?

@regis Sumac.3 Release Ceremony i will be trying to do that on the day of sumac.3 and then update this thread :slight_smile:

This is done :slight_smile: cc: @kmccormick