[ruby-core:106376] [Ruby master Bug#18371] Release branches (release information in general)

Issue #18371 has been updated by hsbt (Hiroshi SHIBATA).

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

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

It's totally release manager's convenience.

----------------------------------------
Bug #18371: Release branches (release information in general)
https://bugs.ruby-lang.org/issues/18371#change-95012

* Author: tenderlovemaking (Aaron Patterson)
* Status: Assigned
* Priority: Normal
* Assignee: naruse (Yui NARUSE)
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
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!



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>