Misc #15614
closedDevelopersMeeting20190311Japan
Description
Please comment your favorite ticket numbers you want to ask to discuss with your SHORT comment or summary.
(your summary/comment will help us because we don't need to read all of ticket comments)
DO NOT discuss then on this ticket, please.
Date: 2019/03/11 (Mon)
Time: 13:00-17:00 (JST)
Place: MoneyForward.com (Tokyo, Japan)
Sign-up: https://ruby.connpass.com/event/120056/
log: https://docs.google.com/document/d/e/2PACX-1vTUCmj7aUdnMAdunG0AZo0AdWK-9jvfXcB7DWYmzGtmPc0IuIPGn7eLARoR5tBd6XUUB08W-hH74k-T/pub
logedit: https://docs.google.com/document/d/1XJKSfrf4ObXEvSOnPEsjGKuwKwzZTtfIb44qS_A5BWY/edit#
NOTES¶
- Dev meeting IS NOT a decision making place. All decisions should be done at the bug tracker.
- Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
- Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
- We will write a log about discussion to a file or to each ticket in English.
- All activities are best-effort (keep in mind that most of us are volunteer developers).
- The date, time and place is scheduled according to when/where we can reserve Matz's time.
Agenda¶
Next dev-meeting¶
About 2.7 timeframe¶
Check security tickets¶
Carry-over from previous meeting(s)¶
From Attendees¶
From non-attendees¶
Please comment your favorite ticket we need to discuss with the following format.
* [Ticket ref] Ticket title (your name)
* your comment why you want to put this ticket here if you want to add.
Your comment is very important if you are no attendee because we can not ask why you want to discuss about it.
Example:
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
* I feel this feature is very useful and some people say :+1: so let discuss about this feature.
We don't guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).
Updated by Glass_saga (Masaki Matsushita) over 5 years ago
- Related to Misc #14770: [META] DevelopersMeeting added
Updated by aycabta (aycabta .) over 5 years ago
- [Feature #14609]
Kernel#p
without args shows the receiver (aycabta)- carry over
Updated by Glass_saga (Masaki Matsushita) over 5 years ago
- Related to Misc #15615: File.birthtimeがLinux環境で有効なファイル作成時刻を得られなかった場合の挙動について added
Updated by Glass_saga (Masaki Matsushita) over 5 years ago
- Related to deleted (Misc #15615: File.birthtimeがLinux環境で有効なファイル作成時刻を得られなかった場合の挙動について)
Updated by Glass_saga (Masaki Matsushita) over 5 years ago
[Misc #15615] File.birthtimeがLinux環境で有効なファイル作成時刻を得られなかった場合の挙動について
Updated by osyo (manga osyo) over 5 years ago
- [Feature #14799] Startless range
- What kind of situation is it? I want it quickly :)
Updated by alanwu (Alan Wu) over 5 years ago
- [Bug #15620] Block argument usage affects lambda semantic
- I find the current behaviour very non-rubyish and would love to hear what core devs think
Updated by blowmage (Mike Moore) over 5 years ago
- [Misc #15617] Release 2.5.4? (blowmage)
- There are several bug fixes backported to 2.5 that have not been released yet. Do we know when they will be released?
Updated by duerst (Martin Dürst) over 5 years ago
- [Feature #15195] How to deal with new Japanese era
- Just adding this to the list so that we can (re)check how we want to proceed.
Updated by alfonsojimenez (Alfonso Jiménez) over 5 years ago
- [Feature #15323] Proposal: Add
Enumerable#filter_map
- I would like to hear more feedback about this feature proposal
Updated by osyo (manga osyo) over 5 years ago
Updated by akr (Akira Tanaka) over 5 years ago
Updated by knu (Akinori MUSHA) over 5 years ago
[Feature #15618] Implement Enumerator::Yielder#to_proc
Updated by hsbt (Hiroshi SHIBATA) over 5 years ago
[Bug #15652] Profiler__ is not working correctly (ruby 2.6)
Updated by akr (Akira Tanaka) over 5 years ago
[Feature #15553] Addrinfo.getaddrinfo supports timeout
Updated by hsbt (Hiroshi SHIBATA) over 5 years ago
- Status changed from Open to Closed
The next meeting issue is here: https://bugs.ruby-lang.org/issues/15459