[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>
I would like to request developers meeting around April 17 or 18 in this month.
14 messages
2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014
— Urabe Shyouhei <shyouhei@...>
2014/04/03
It's good if we have a meeting then.
[#61826] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/03
Regarding openssl issues, I’ve discussed possible meeting time with Martin last month and he seemed positive.
[#61833] Re: Plan Developers Meeting Japan April 2014
— Martin Bo煬et <martin.bosslet@...>
2014/04/03
Hi,
[#61847] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/03
Martin Boテ殕et <martin.bosslet@gmail.com> wrote:
[#61849] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I will post summary of meeting on Google docs after the meeting.
[#61852] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/04
Zachary Scott <e@zzak.io> wrote:
[#61860] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I’m ok with redmine, thanks for bringing up your concern!
[#62076] Candidacy to 2.1 branch maintainer. — Tomoyuki Chikanaga <nagachika00@...>
Hello,
7 messages
2014/04/17
[#62078] Re: Candidacy to 2.1 branch maintainer.
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/04/17
> And does anyone have counter proposal for 2.1 maintenance?
[ruby-core:61867] [ruby-trunk - Bug #9660] test/unit, minitest & bundler
From:
robin.dupret@...
Date:
2014-04-05 14:21:57 UTC
List:
ruby-core #61867
Issue #9660 has been updated by Robin Dupret.
Hello,
I take the liberty to link to a branch with a beginning of patch that updates the bundled version of Minitest to 5 (https://github.com/robin850/ruby/compare/minitest-five) since this is more or less related to the problem here. IMO, this is really bad to have a "deprecated"/out dated version of a library that you're shipping with by default. I'm conscious that the amount of work would be pretty important to rename all `Test::Unit::TestCase` classes to `Minitest::Test` but the wrapper is not so nice.
Moreover, I don't think the amount of work needed to rename the test suite is really worth regarding the final result. The test cases would have to be renamed anyway if we follow Zachary's suggestion (which is legit, I think ; it would make no sense to have a ruby/unit.rb file with a `Test::Unit` class in it).
I find it sometimes annoying to have to create a Gemfile adding `gem 'minitest'` in it just to use an up to date version of Minitest.
I'm pretty sure you have good reasons to stuck with Test::Unit inside your test suite, but just my two cents here.
Have a nice day.
----------------------------------------
Bug #9660: test/unit, minitest & bundler
https://bugs.ruby-lang.org/issues/9660#change-46084
* Author: Marc-Andre Lafortune
* Status: Open
* Priority: High
* Assignee: Shota Fukumori
* Category: lib
* Target version: current: 2.2.0
* ruby -v: r45033
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
test/unit now calls `gem 'minitest'`, but this will create regressions for anyone using `bundler`.
For example, create an empty `Gemfile` and try `bundle exec ruby -e "require 'test/unit'"`
You get an error:
.rvm/gems/ruby-head@global/gems/bundler-1.5.3/lib/bundler/rubygems_integration.rb:240:in `block in replace_gem': minitest is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
See: https://github.com/ruby/ruby/commit/da61291a25faae95f33de6756b2eaa4804d5ef2b#commitcomment-5761129
--
https://bugs.ruby-lang.org/