Project

General

Profile

Actions

Misc #18371

open

Release branches (release information in general)

Added by tenderlovemaking (Aaron Patterson) 10 months ago. Updated 6 months ago.

Status:
Assigned
Priority:
Normal
[ruby-core:106351]

Description

Hi,

I was trying to learn about Ruby's release process. I noticed that we don't create a release branch until the final version is shipped. Is there a reason we don't create the release branch when the first preview is shipped? The reason I'm asking is because I'm worried about merging things to master after the first preview. Do we have any documentation on the release process? (I was searching and couldn't find much info, but maybe I didn't search correctly)

Thanks!

Updated by hsbt (Hiroshi SHIBATA) 10 months ago

In recent years, we released the final version of new release from master branch directly. Because creating the release branch before the final release is hard work to backport for release manager.

Updated by Eregon (Benoit Daloze) 10 months ago

when the first preview is shipped

Do you mean when the first RC is shipped?
Previews can be early in the dev cycle and don't prevent new features being added after AFAIK.

Updated by tenderlovemaking (Aaron Patterson) 10 months ago

Eregon (Benoit Daloze) wrote in #note-2:

when the first preview is shipped

Do you mean when the first RC is shipped?
Previews can be early in the dev cycle and don't prevent new features being added after AFAIK.

So is RC the point when we create a branch? I guess I'm just not clear on when release branches get made.

Updated by hsbt (Hiroshi SHIBATA) 10 months ago

  • Status changed from Open to Assigned
  • Assignee set to naruse (Yui NARUSE)

I guess I'm just not clear on when release branches get made.

It's totally release manager's convenience.

Updated by mame (Yusuke Endoh) 10 months ago

tenderlovemaking (Aaron Patterson) wrote in #note-3:

So is RC the point when we create a branch? I guess I'm just not clear on when release branches get made.

The trend for the past few years has been to branch on the day of the official release, i.e., 25th Dec. This is based on the experience that if we branch in advance, we need a lot of backporting. Therefore, it is supposed that we do not commit too drastic changes in December. Unfortunately, this is implicit knowledge and there is no documentation.

Based on the experience of Ruby's release manager burning out, naruse-san prioritizes saving any labor in the release management.

Updated by duerst (Martin Dürst) 10 months ago

On 2021-12-02 09:24, tenderlovemaking (Aaron Patterson) wrote:

Issue #18371 has been updated by tenderlovemaking (Aaron Patterson).

Eregon (Benoit Daloze) wrote in #note-2:

when the first preview is shipped

Do you mean when the first RC is shipped?
Previews can be early in the dev cycle and don't prevent new features being added after AFAIK.

So is RC the point when we create a branch? I guess I'm just not clear on when release branches get made.

As far as I understand, every year is a bit different. It depends on the
release manager's time and on how much surprises are suspected (somewhat
of a contradiction, but I hope you get the point).

Regards, Martin.

Actions #7

Updated by jeremyevans0 (Jeremy Evans) 6 months ago

  • Tracker changed from Bug to Misc
  • Backport deleted (2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN)
Actions

Also available in: Atom PDF