[#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:92853] [Ruby trunk Misc#15874] DevelopersMeeting20190613Japan
From:
s+ruby@...
Date:
2019-05-27 01:00:33 UTC
List:
ruby-core #92853
Issue #15874 has been updated by sikachu (Prem Sichanugrist).
* [Feature #15725] Add Array#reverse_sort, #revert_sort!, #reverse_sort_by, and #reverse_sort_by!
I would like to propose these methods as the preferred way for developers to create reverse sorted array, which is to call `sort(_by).reverse!` internally. By introduce these methods, we can discourage user to use them instead of do `array.sort.reverse` (without bang) or `array.sort { |a, b| b <=> a }` which would create an unnecessary Array (after `.sort).
----------------------------------------
Misc #15874: DevelopersMeeting20190613Japan
https://bugs.ruby-lang.org/issues/15874#change-78234
* Author: mame (Yusuke Endoh)
* 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 ticket comments)
*DO NOT* discuss then on this ticket, please.
----
Date: 2019/06/13 (Wed)
Time: 14:00-17:30 (JST)
Place and Sign-up: https://ruby.connpass.com/event/132888/
log: https://docs.google.com/document/d/1XP_e-3utXlCaxZLJrov6c428ZNaMPmxa3eh9MASrzkI/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)
None.
## 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).
--
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>