[#92891] Question: ruby 2.7.0-preview1 also upgrades bundler to 2.1.0.pre.1? — Al Snow <jasnow@...>
Tried the new 2.7.0-preview1 upgrade to Ruby and see that bundler is also u=
5 messages
2019/05/30
[#92892] Re: Question: ruby 2.7.0-preview1 also upgrades bundler to 2.1.0.pre.1?
— SHIBATA Hiroshi <hsbt@...>
2019/05/30
Bundler 2.1.0.pree.1 is the expected version.
[#92893] Re: Question: ruby 2.7.0-preview1 also upgrades bundler to 2.1.0.pre.1?
— Al Snow <jasnow@...>
2019/05/30
[ruby-core:92512] [Ruby trunk Misc#15782] DevelopersMeeting20190522Japan
From:
lourens@...
Date:
2019-05-01 10:07:41 UTC
List:
ruby-core #92512
Issue #15782 has been updated by methodmissing (Lourens Naud=E9). * [Misc #15800] [PATCH] Reduce `ONIG_NREGION` size from 10 to 4 * Power of 2 and testing revealed most pattern matches are less than or eq= ual to 4 results * `MatchData` instances over allocate memory for the most common cases * [Misc #15802] [PATCH] Reduce the minimum string buffer size from 127 to 6= 3 bytes * The most common case for string buffers in Rails processes are less than= 63 bytes ---------------------------------------- Misc #15782: DevelopersMeeting20190522Japan https://bugs.ruby-lang.org/issues/15782#change-77875 * Author: k0kubun (Takashi Kokubun) * Status: Open * Priority: Normal * Assignee: = ---------------------------------------- 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 tic= ket comments) *DO NOT* discuss then on this ticket, please. ---- Date: 2019/05/22 (Wed) Time: 13:00-17:00 (JST) Place: pixiv (Tokyo, Japan) Sign-up: https://ruby.connpass.com/event/129507/ log: TODO logedit: TODO # NOTES - Dev meeting *IS NOT* a decision making place. All decisions should be don= e 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 unders= tand your issue). - We will write a log about discussion to a file or to each ticket in Engli= sh. - All activities are best-effort (keep in mind that most of us are voluntee= r developers). - The date, time and place is scheduled according to when/where we can rese= rve 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 as= k 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 disc= uss about this feature. ``` We don't guarantee to put tickets in agenda if the comment violate the form= at (because it is hard to copy&paste). -- = https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=3Dunsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>