[#101981] [Ruby master Bug#17519] set_visibility fails when a prepended module and a refinement both exist — dbfeldman@...

Issue #17519 has been reported by fledman (David Feldman).

12 messages 2021/01/08

[#102003] [Ruby master Bug#17527] rb_io_wait_readable/writable with scheduler don't check errno — julien@...

Issue #17527 has been reported by ysbaddaden (Julien Portalier).

13 messages 2021/01/11

[#102065] [Ruby master Bug#17536] Segfault in `CFUNC :define_method` — v.ondruch@...

Issue #17536 has been reported by vo.x (Vit Ondruch).

13 messages 2021/01/13

[#102083] [Ruby master Bug#17540] A segfault due to Clang/LLVM optimization on 32-bit ARM Linux — xtkoba+ruby@...

Issue #17540 has been reported by xtkoba (Tee KOBAYASHI).

12 messages 2021/01/14

[#102102] [Ruby master Bug#17543] Ractor isolation broken by `self` in shareable proc — marcandre-ruby-core@...

Issue #17543 has been reported by marcandre (Marc-Andre Lafortune).

14 messages 2021/01/15

[#102118] [Ruby master Feature#17548] Need simple way to include symlink directories in Dir.glob — keithrbennett@...

Issue #17548 has been reported by keithrbennett (Keith Bennett).

8 messages 2021/01/17

[#102158] [Ruby master Bug#17560] Does `Module#ruby2_keywords` return `nil` or `self`? — nobu@...

Issue #17560 has been reported by nobu (Nobuyoshi Nakada).

9 messages 2021/01/19

[#102163] [Ruby master Bug#17561] The timeout option for Addrinfo.getaddrinfo is not reliable on Ruby 2.7.2 — sean@...

Issue #17561 has been reported by smcgivern (Sean McGivern).

8 messages 2021/01/19

[#102249] [Ruby master Bug#17583] Segfault on large stack(RUBY_THREAD_VM_STACK_SIZE) — yoshiokatsuneo@...

Issue #17583 has been reported by yoshiokatsuneo (Tsuneo Yoshioka).

12 messages 2021/01/26

[#102256] [Ruby master Bug#17585] DWAR5 support? — v.ondruch@...

Issue #17585 has been reported by vo.x (Vit Ondruch).

19 messages 2021/01/26

[#102301] [Ruby master Bug#17591] Test frameworks and REPLs do not show deprecation warnings by default — eregontp@...

Issue #17591 has been reported by Eregon (Benoit Daloze).

14 messages 2021/01/29

[#102305] [Ruby master Feature#17592] Ractor should allowing reading shareable class instance variables — marcandre-ruby-core@...

Issue #17592 has been reported by marcandre (Marc-Andre Lafortune).

25 messages 2021/01/29

[ruby-core:101849] [Ruby master Misc#17499] Documentation backporting

From: zverok.offline@...
Date: 2021-01-01 12:09:45 UTC
List: ruby-core #101849
Issue #17499 has been reported by zverok (Victor Shepelev).

----------------------------------------
Misc #17499: Documentation backporting
https://bugs.ruby-lang.org/issues/17499

* Author: zverok (Victor Shepelev)
* Status: Open
* Priority: Normal
----------------------------------------
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](https://github.com/ruby/docs.ruby-lang.org/issues/111) I was educated by @hsbt 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):
* `doc/syntax/pattern_matching.rdoc`: [merged](https://github.com/ruby/ruby/pull/2786) on 2020-02-23, but is not represented here: https://docs.ruby-lang.org/en/2.7.0/ -- because it isn't present in [ruby_2_7](https://github.com/ruby/ruby/tree/ruby_2_7/doc/syntax) branch.
* update `doc/syntax/methods.rdoc` (add endless methods and `...`-forwarding): [merged](https://github.com/ruby/ruby/pull/3997) 2020-12-25 (just a few hours after 3.0 release), but not represented here: https://docs.ruby-lang.org/en/3.0.0/doc/syntax/methods_rdoc.html -- because it isn't in [ruby_3_0](https://github.com/ruby/ruby/blob/ruby_3_0/doc/syntax/methods.rdoc) branch.

**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?..)



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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next