closer changed the topic of #ruby-core to: check the latest release candidate for 1.9.1 release ftp.ruby-lang.org:/home/yugui/ruby-1.9.1-r26021+1.tar.bz2
nokada has joined #ruby-core
nokada_ has quit [Read error: Connection reset by peer]
<znz_jp>
biff: [ruby-changes:41436] duerst:r53510 (trunk): string.c: made a variable name more grammatically correct - http://mla.n-z.jp/?ruby-changes=41436
hsbt_away has joined #ruby-core
djellemah has quit [Ping timeout: 240 seconds]
djellemah has joined #ruby-core
nokada has quit [Remote host closed the connection]
nokada has joined #ruby-core
hsbt_away is now known as hsbt
nagachika has joined #ruby-core
nokada has quit [Read error: Connection reset by peer]
nokada has joined #ruby-core
<znz_jp>
biff: [ruby-changes:41437] sorah:r53511 (trunk): * lib/forwardable.rb: Convert given accessors to String. - http://mla.n-z.jp/?ruby-changes=41437
nagachika has quit [Remote host closed the connection]
brixen has quit [Ping timeout: 276 seconds]
brixen has joined #ruby-core
nagachika has joined #ruby-core
<znz_jp>
biff: [ruby-changes:41439] eregon:r53513 (trunk): * common.mk: update URL and name for the Ruby spec suite. - http://mla.n-z.jp/?ruby-changes=41439
Windir has quit [Remote host closed the connection]
nagachika has quit [Remote host closed the connection]
ItSANgo has quit [Quit: Leaving...]
<eregon>
nurse, nokada: are you here?
<hsbt>
I vote "rubytest" instead of "spec"
<eregon>
hsbt: ruby/rubytest?
<eregon>
I find "Ruby test suite" confusing with MRI's suite
<eregon>
and there are quite important differences between the two as well
ItSANgo has joined #ruby-core
<eregon>
it's unfortunate that BDD specifications (like in RSpec) are also using "specification", but for a fairly different meaning
<nurse>
ah, here
<nurse>
Foundamentally I concern why rubyspec is bad but ruby/spec is fine.
<nurse>
Anyway I found headius pros ruby/spec, hmm.
<eregon>
yes, that convinced me, since everyone seemed to agree on it
<eregon>
repo name can be fixed if that's the issue (maybe ruby/spec_suite ruby/ruby_spec_suite ?)
<eregon>
nurse: Could you summarize in a few words what's the opinion on #ruby-ja? automatic translation is too bad it seems
<nurse>
well,
<nurse>
I (and hsbt seems) ruby/spec (The Ruby Spec Suite) is not changed the name, it still RubySpec.
<nurse>
But I now think headius says ruby/spec / The Ruby Spec Suite is fine, it is fine because
<eregon>
yes, pretty much, if Brian didn't ask to change and matz didn't say we should change, I would not bother to change the name either
<nurse>
if it is not actually changed, the confusing "spec" name is also unchanged.
<eregon>
and it seems Brian is fine with ruby/spec from what appears on the issue
<hsbt>
Does it solve brixen's concerns? I worry it.
<hsbt>
fmm
<nurse>
brixen's main concern seems "What is new RubySpec".
<eregon>
yes it seems, since it's @jc00ke, a friend of Brian which proposed it. I think he cares only about the term "RubySpec"
<eregon>
about the "What is new RubySpec", I gave a quick a quick try on https://github.com/ruby/spec, but it is worth a discussion on the rubyc-ore mailing-list
<nokada>
behavior_suite?
<eregon>
nokada: I like the idea but it sounds strange: The Ruby behavior suite
<nokada>
indeed
<nokada>
behavior check suit
<eregon>
one idea with the current name is that, as headius said, it's just Ruby's spec/, like many Ruby projects would have a spec/ dir, and that's not for formal specifications, it's just a different way of testing
<znz_jp>
biff: [ruby-changes:41443] naruse:r53517 (trunk): drop osx and clang because they are often fails and slow - http://mla.n-z.jp/?ruby-changes=41443
<headius>
I'm find with calling it a spec suite because the format is widely accepted as "spec" based testing by Rubyists
<headius>
rspec did it first...mspec duplicated most of what rspec did and added tagging and masks and other features
<headius>
but the format is still obviously "spec"
<headius>
nurse, eregon: ^
<eregon>
nurse, hsbt, nokada_: if any of you or ruby-core still has concern about the current name, please express it here :)
<eregon>
I would be happy if I don't need to change the name again, but if there is a good motivation and we find a better name, we can re-rename
<eregon>
I am sorry to not have asked you directly before choosing it (I thought you followed the issue and everyone seemed to agree on ruby/spec). We can discuss it on the ML as well if you prefer
nagachika has joined #ruby-core
nagachika has quit [Remote host closed the connection]