ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: sam.saffron@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:103864] [Ruby master Misc#17811] DevelopersMeeting20210521Japan
Date: Mon, 17 May 2021 04:15:08 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-91990.20210517041507.18@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17811.20210417081829.18@ruby-lang.org

Issue #17811 has been updated by sam.saffron (Sam Saffron).


[Bug #17781] Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang

   - Security issue is quite severe (can cause denial of service), any chance we can do a 2.7.4 release shortly? 





----------------------------------------
Misc #17811: DevelopersMeeting20210521Japan
https://bugs.ruby-lang.org/issues/17811#change-91990

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2021/05/21 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*

- 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 the 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 are scheduled according to when/where we can reserve Matz's time.
- *DO NOT* discuss then on this ticket, please.

# Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

```
* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
```

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 this feature.
```

- It is recommended to add a comment by 2021/05/18. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
- The format is strict.  We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86).  We may ignore a comment that does not follow the format.
- Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion.




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

  parent reply	other threads:[~2021-05-17  4:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17  8:18 [ruby-core:103498] [Ruby master Misc#17811] DevelopersMeeting20210521Japan mame
2021-05-10 20:21 ` [ruby-core:103778] " merch-redmine
2021-05-11  9:12 ` [ruby-core:103782] " jean.boussier
2021-05-13 10:07 ` [ruby-core:103832] " duerst
2021-05-13 15:40 ` [ruby-core:103837] " XrXr
2021-05-17  2:38 ` [ruby-core:103863] " ko1
2021-05-17  4:15 ` sam.saffron [this message]
2021-05-20 10:47 ` [ruby-core:103913] " hsbt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-91990.20210517041507.18@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).