# Git checkout release/teak.master

**URL:** <https://discuss.openedx.org/t/git-checkout-release-teak-master/15618>\
**Category:** Build-Test-Release\
**Created:** [April 26, 2025, 7:58am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618 "2025-04-26T07:58:15Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [April 26, 2025, 7:58am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/1 "2025-04-26T07:58:15Z")

</div>

Open edX developers! We just created the `release/teak.master` branch in 34 Open edX repositories. ⚠ THESE BRANCHES ARE NOT FOR PUBLIC CONSUMPTION ⚠ 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](https://github.com/openedx/build-test-release-wg/issues/) board.

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

```auto
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

```

---

<div class="post-metadata">

**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\
**Post date:** [April 28, 2025, 5:28pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/2 "2025-04-28T17:28:07Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [April 28, 2025, 5:43pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/3 "2025-04-28T17:43:52Z")

</div>

yes @sarina it was decided in [Should we rename the release branches? - #12 by kmccormick](https://discuss.openedx.org/t/should-we-rename-the-release-branches/8827/12), that the coming release should have release instead of open-release. It was planned for Sumac but ended up doing that in Teak.

---

<div class="post-metadata">

**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\
**Post date:** [April 28, 2025, 5:49pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/4 "2025-04-28T17:49:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [April 28, 2025, 7:43pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/5 "2025-04-28T19:43:45Z")

</div>

oops! thank you so much @sarina 🙂

---

<div class="post-metadata">

**Author:** ![regis](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/regis/32/2640_2.png) [@regis](https://discuss.openedx.org/u/regis)\
**Post date:** [April 29, 2025, 6:50am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/6 "2025-04-29T06:50:14Z")

</div>

🤔 Didn’t we [agree](https://github.com/openedx/.github/blob/master/docs/decisions/0002-namespacing-branches.rst#decisions) to name the branches `release/teak` and not `release/teak.master`? What’s the use of the “.master” suffix? 👀 @kmccormick

---

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [April 29, 2025, 8:42am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/7 "2025-04-29T08:42:36Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![regis](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/regis/32/2640_2.png) [@regis](https://discuss.openedx.org/u/regis)\
**Post date:** [April 29, 2025, 9:10am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/8 "2025-04-29T09:10:56Z")

</div>

It’s OK. Can we rename the branches?

---

<div class="post-metadata">

**Author:** ![kmccormick](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/kmccormick/32/8982_2.png) [@kmccormick](https://discuss.openedx.org/u/kmccormick)\
**Post date:** [April 29, 2025, 1:52pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/9 "2025-04-29T13:52:27Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [April 30, 2025, 11:59am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/10 "2025-04-30T11:59:14Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![regis](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/regis/32/2640_2.png) [@regis](https://discuss.openedx.org/u/regis)\
**Post date:** [May 12, 2025, 11:55am UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/11 "2025-05-12T11:55:03Z")

</div>

@farhaanbukhsh any update on the branch renaming?

---

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [May 14, 2025, 12:09pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/12 "2025-05-14T12:09:37Z")

</div>

@regis [Sumac.3 Release Ceremony](https://discuss.openedx.org/t/sumac-3-release-ceremony/15848) i will be trying to do that on the day of sumac.3 and then update this thread 🙂

---

<div class="post-metadata">

**Author:** ![farhaanbukhsh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/farhaanbukhsh/32/1503_2.png) [@farhaanbukhsh](https://discuss.openedx.org/u/farhaanbukhsh)\
**Post date:** [May 19, 2025, 4:06pm UTC](https://discuss.openedx.org/t/git-checkout-release-teak-master/15618/13 "2025-05-19T16:06:28Z")

</div>

This is done 🙂 cc: @kmccormick
