Project

General

Profile

Actions

Misc #17499

closed

Documentation backporting

Added by zverok (Victor Shepelev) 7 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
[ruby-core:101849]

Description

I recently noticed that the documentation created after x.y release (even 1 day after) never reflected at docs.ruby-lang.org/<x.y>.0/.

In discussion here I was educated by hsbt (Hiroshi SHIBATA) that the source of docs.ruby-lang.org/<x.y>.0/ is actually a branch ruby_<x_y>, so in order to appear at docs.ruby-lang.org, documentation should be "backported" into the proper branch, which usually does not happen.

A few examples (documentation submitted by me, but it is not that I consider "my" documentation the most important, it is just easier for me to track):

IMPORTANT: It is just two random examples, I believe there are numerous problems like that.

I wonder how this should be addressed:

  • should somebody gather all the occurrences to "commits that should be picked into the proper branches"?
  • can it be done in some systematic manner?
  • can at least currently developed (3.0's) enhancements be "backported" in some automatic manner (PR labels?..)
Actions

Also available in: Atom PDF