ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:99376] [Ruby master Misc#17041] DevelopersMeeting20200826Japan
Date: Tue, 28 Jul 2020 22:07:29 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-86781.20200728220728.18@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17041.20200722055527.18@ruby-lang.org

Issue #17041 has been updated by jeremyevans0 (Jeremy Evans).


* [Feature #17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings (jeremyevans0)
  * This keeps the default behavior the same as before, but allows opt-in to supress the warnings.
  * This allows for high-performance code (uninitialized instance variables) and safe code (redefining methods without removing in multi-thread environments) to work without issuing warnings in verbose mode.
  * Is it OK to commit the patch?

----------------------------------------
Misc #17041: DevelopersMeeting20200826Japan
https://bugs.ruby-lang.org/issues/17041#change-86781

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

**Date: 2020/08/26 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.
```

- Comment deadline: 2020/08/19 (one week before the 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.




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

  parent reply	other threads:[~2020-07-28 22:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  5:55 [ruby-core:99257] [Ruby master Misc#17041] DevelopersMeeting20200826Japan mame
2020-07-22  5:58 ` [ruby-core:99258] " zn
2020-07-22  6:06 ` [ruby-core:99259] " shyouhei
2020-07-22  8:04 ` [ruby-core:99261] " mame
2020-07-22 17:28 ` [ruby-core:99271] " marcandre-ruby-core
2020-07-28 22:07 ` merch-redmine [this message]
2020-08-01 13:27 ` [ruby-core:99437] " eregontp
2020-08-03 15:55 ` [ruby-core:99455] " daniel
2020-08-04  8:32 ` [ruby-core:99475] " jean.boussier
2020-08-06 10:14 ` [ruby-core:99498] " eregontp
2020-08-09  8:19 ` [ruby-core:99521] " jean.boussier
2020-08-09 18:53 ` [ruby-core:99525] " eregontp
2020-08-19  5:15 ` [ruby-core:99637] " zn
2020-08-19 16:26 ` [ruby-core:99644] " mame
2020-08-25 22:39 ` [ruby-core:99691] " muraken
2020-08-26  1:16 ` [ruby-core:99693] " muraken
2020-08-26  8:40 ` [ruby-core:99704] " mame
2020-08-27  7:43 ` [ruby-core:99727] [Ruby master Misc#17041] DevelopersMeeting20200831Japan duerst

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-86781.20200728220728.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).