After so many years my fingers are tired of typing long branch names such as “open-release/nutmeg.master”. I propose that for Palm we name the release branch “release/palm”. Then, release tags should be named “release/palm.beta1”, “release/palm.1”, etc. To ease the transition, I propose that we also…

This doesn’t have to block your proposal, but one of the reasons we didn’t name the branches that way to start was that we already had branches (and tags) starting with “release” for the deploys to edx.org , though they don’t have the slash.

To start with… YES, PLEASE! :slight_smile: My motivation is less a practical one and more philosophical, though. As compared to some other open source communities, I’ve always thought that the way Open edX distinguishes between what is community-facing and what is edx.org-specific a little… backwa…

I agree that our de facto process for managing releses might not be efficient, I hope this or any future change would adress the following issues or pain points: Make it easy to backport a commit(s) to the release branch Make it possible to release a particular repo/compoenent/IDA…etc without rely…

[image] arbrandes: “Open source PRs” (OSPRs) and the case in point, “open-release” are two terms that I’d love to see changed into “PRs” and “releases”. And if by any chance the distinction needs to persist, it should go the other way: “edx PRs” and “edx-org-release” I think this it’s the cor…

[image] ghassan: For 2, to give you an example, imagine a particular MFE, got an important necessary fix, just one day after we release olive.1. Now should that MFE wait for olive.2? so people can use it… Of course there is a way around to set the branch/commit-id in tutor-mfe… but I don’t think…

I’m supportive of doing this over time, but would like to hear from @jmbowman on what would be a reasonable amount of time for continuous delivery to be updated. I’ll note that the original post proposed making the change because “open-release” was too long to type. The thread has evolved :wink: I…

I’ve started an ADR to advance this conversation. E0d/namespace adr openedx:master ← e0d:e0d/namespace-adr opened 10:36PM - 07 Dec 22 UTC (UTC) [e0d] …

[image] regis: In Tutor, we address this issue by cherry-picking individual commits between minor releases. This is not ideal, but it’s the best I can do. @ghassan do you have any better idea? I don’t have a spesfic thing in mind, I can specualte it can be something like: A depencey of tuto…

[image] ghassan: I don’t have a spesfic thing in mind, I can specualte it can be something like: A depencey of tutor/tutor-plugin released a new tag A web hook from that repo trigger tutor CI/CD to build the image with new tag A new image of that tutor service is relelesed. Yes, this is pre…

Latest updates on this: Ed’s ADR, linked above, has been merged. The release/ namespace will be available for BTR to use starting in Sumac .

Should we rename the release branches?

Working Groups Build-Test-Release

kmccormick (Kyle McCormick) April 2, 2024, 7:35pm 11

Latest updates on this:

Ed’s ADR, linked above, has been merged.
The release/ namespace will be available for BTR to use starting in Sumac.

Git checkout open-release/sumac.master

TEP: Rename nightly->next and master->release

Topic		Replies	Views
Git checkout release/teak.master Build-Test-Release	12	196	May 19, 2025
Git checkout open-release/sumac.master Working Groups	4	99	October 28, 2024
Tagging releases? Useful or not? Build-Test-Release	21	2495	October 2, 2020
TEP: Rename nightly->next and master->release Releases tutor , tutor-plugin	10	355	November 27, 2024
Palm master branches are coming Development	1	345	April 6, 2023

Should we rename the release branches?

Related topics