hsbt_away 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
closer has joined #ruby-core
havenwood has quit [Remote host closed the connection]
nokada has quit [Remote host closed the connection]
nokada has joined #ruby-core
ayumin has joined #ruby-core
nokada has quit [Ping timeout: 260 seconds]
ayumin has quit [Ping timeout: 252 seconds]
nokada has joined #ruby-core
ayumin has joined #ruby-core
eLobato|away has quit [Ping timeout: 245 seconds]
ayumin has quit [Ping timeout: 272 seconds]
Philpax has joined #ruby-core
<zzak> hsbt: i'd really like to announce the maintenance policy soon, could you review my post?
<zzak> its important people understand the release cycle for patch levels
soba has joined #ruby-core
nari has joined #ruby-core
ayumin has joined #ruby-core
ayumin has quit [Ping timeout: 272 seconds]
charliesome has joined #ruby-core
<znz_jp> biff: [ruby-changes:32546] nobu:r44625 (trunk): common.mk: fix command error - http://mla.n-z.jp/?ruby-changes=32546
<znz_jp> biff: [ruby-changes:32547] nobu:r44626 (trunk): test_rinda.rb: timeout all thread - http://mla.n-z.jp/?ruby-changes=32547
<znz_jp> biff: [ruby-changes:32548] nobu:r44627 (trunk): test_thread.rb: stop at once - http://mla.n-z.jp/?ruby-changes=32548
tylersmith has quit [Remote host closed the connection]
knu has quit [Ping timeout: 252 seconds]
knu has joined #ruby-core
r0bgleeson has quit [Ping timeout: 272 seconds]
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 272 seconds]
marcandre has quit [Remote host closed the connection]
nari has quit [Ping timeout: 276 seconds]
eLobato|away has joined #ruby-core
eLobato|away is now known as eLobato
r0bgleeson has joined #ruby-core
soba has quit [Ping timeout: 276 seconds]
nari has joined #ruby-core
eLobato is now known as eLobato|away
marcandre has joined #ruby-core
enebo has joined #ruby-core
marcandre has quit [Remote host closed the connection]
shinnya has joined #ruby-core
ZachBeta has joined #ruby-core
eLobato|away has quit [Read error: Operation timed out]
eLobato|away has joined #ruby-core
eLobato|away is now known as eLobato
anveo has joined #ruby-core
nari has quit [Read error: Operation timed out]
tylersmith has joined #ruby-core
rafaelfranca has joined #ruby-core
nari has joined #ruby-core
nagachika has joined #ruby-core
nari has quit [Ping timeout: 245 seconds]
eLobato has quit [Ping timeout: 245 seconds]
havenwood has joined #ruby-core
marcandre has joined #ruby-core
enebo has quit [Quit: enebo]
shinnya has quit [Ping timeout: 245 seconds]
charlies_ has joined #ruby-core
charliesome has quit [Ping timeout: 272 seconds]
eLobato has joined #ruby-core
charlies_ has quit [Ping timeout: 252 seconds]
charliesome has joined #ruby-core
ZachBeta has quit [Ping timeout: 252 seconds]
nagachika has quit [Remote host closed the connection]
nagachika has joined #ruby-core
samkottler has quit [Ping timeout: 252 seconds]
Philpax has quit [Read error: Connection reset by peer]
samkottler has joined #ruby-core
samkottler has quit [Changing host]
samkottler has joined #ruby-core
nagachika has quit [Remote host closed the connection]
enebo has joined #ruby-core
ZachBeta has joined #ruby-core
rafaelfranca has quit [Remote host closed the connection]
rafaelfranca has joined #ruby-core
rafaelfranca has quit [Remote host closed the connection]
heroux has quit [Ping timeout: 264 seconds]
eLobato has quit [Ping timeout: 248 seconds]
heroux has joined #ruby-core
rafaelfranca has joined #ruby-core
cout is now known as timelord_cout
someguy has quit [Quit: Page closed]
eLobato has joined #ruby-core
rafaelfr_ has joined #ruby-core
rafaelfranca has quit [Read error: Connection reset by peer]
eLobato has quit [Ping timeout: 272 seconds]
shinnya has joined #ruby-core
ZachBeta has quit [Quit: Computer has gone to sleep.]
eLobato has joined #ruby-core
rafaelfr_ has quit [Read error: Connection reset by peer]
rafaelfranca has joined #ruby-core
postmodern has joined #ruby-core
<postmodern> so rubysec is discussing storing ruby implementation advisories in ruby-advisory-db
<postmodern> with MRI switching to a semver-like versioning scheme
<postmodern> would it be appropriate to represent older versions in 1.2.3.4 form?
<drbrain> postmodern: Gem.ruby_version reports patchlevel for releases as a fourth "digit"
<postmodern> drbrain, ah yes
<postmodern> drbrain, will probably end up using Gem.ruby_version and Gem::Version
bffff has joined #ruby-core
<mpapis> drbrain, oh so Gem.ruby_version for 2.1.1 will be 2.1.1 or 2.1.1.number_of_commits_since_2.1.0 ?
<drbrain> mpapis: the fourth digit is the patchlevel, so I guess?
<drbrain> RUBY_PATCHLEVEL
<mpapis> yes, but in starting with 2.1.0 there is branch 2.1 and 2.1.1 will be released next not 2.1.0-p... but then the post about semver mentioned ruby still will count commits in patchelvel