#ruby-core on 2014-01-16 — irc logs at freenode.irclog.whitequark.org

2013-03-25 00:43 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

00:10 closer has joined #ruby-core

00:16 havenwood has quit [Remote host closed the connection]

00:18 nokada has quit [Remote host closed the connection]

00:18 nokada has joined #ruby-core

00:23 ayumin has joined #ruby-core

00:23 nokada has quit [Ping timeout: 260 seconds]

00:28 ayumin has quit [Ping timeout: 252 seconds]

01:13 nokada has joined #ruby-core

01:17 ayumin has joined #ruby-core

01:18 eLobato|away has quit [Ping timeout: 245 seconds]

01:22 ayumin has quit [Ping timeout: 272 seconds]

01:32 Philpax has joined #ruby-core

01:39 <zzak> hsbt: i'd really like to announce the maintenance policy soon, could you review my post?

01:39 <zzak> its important people understand the release cycle for patch levels

01:54 soba has joined #ruby-core

02:01 nari has joined #ruby-core

02:18 ayumin has joined #ruby-core

02:22 ayumin has quit [Ping timeout: 272 seconds]

03:09 charliesome has joined #ruby-core

05:54 <znz_jp> biff: [ruby-changes:32546] nobu:r44625 (trunk): common.mk: fix command error - http://mla.n-z.jp/?ruby-changes=32546

05:54 <znz_jp> biff: [ruby-changes:32547] nobu:r44626 (trunk): test_rinda.rb: timeout all thread - http://mla.n-z.jp/?ruby-changes=32547

06:34 <znz_jp> biff: [ruby-changes:32548] nobu:r44627 (trunk): test_thread.rb: stop at once - http://mla.n-z.jp/?ruby-changes=32548

06:50 tylersmith has quit [Remote host closed the connection]

07:17 knu has quit [Ping timeout: 252 seconds]

07:18 knu has joined #ruby-core

07:26 r0bgleeson has quit [Ping timeout: 272 seconds]

08:01 tylersmith has joined #ruby-core

08:06 tylersmith has quit [Ping timeout: 272 seconds]

08:39 marcandre has quit [Remote host closed the connection]

09:39 nari has quit [Ping timeout: 276 seconds]

10:01 eLobato|away has joined #ruby-core

10:02 eLobato|away is now known as eLobato

10:08 r0bgleeson has joined #ruby-core

11:51 soba has quit [Ping timeout: 276 seconds]

12:05 nari has joined #ruby-core

13:13 eLobato is now known as eLobato|away

13:56 marcandre has joined #ruby-core

14:14 enebo has joined #ruby-core

14:19 marcandre has quit [Remote host closed the connection]

14:49 shinnya has joined #ruby-core

14:51 ZachBeta has joined #ruby-core

14:51 eLobato|away has quit [Read error: Operation timed out]

14:57 eLobato|away has joined #ruby-core

15:04 eLobato|away is now known as eLobato

15:07 anveo has joined #ruby-core

15:13 nari has quit [Read error: Operation timed out]

15:27 tylersmith has joined #ruby-core

15:34 rafaelfranca has joined #ruby-core

15:42 nari has joined #ruby-core

15:47 nagachika has joined #ruby-core

16:01 nari has quit [Ping timeout: 245 seconds]

16:17 eLobato has quit [Ping timeout: 245 seconds]

17:24 havenwood has joined #ruby-core

17:30 marcandre has joined #ruby-core

17:30 enebo has quit [Quit: enebo]

17:32 shinnya has quit [Ping timeout: 245 seconds]

17:45 charlies_ has joined #ruby-core

17:49 charliesome has quit [Ping timeout: 272 seconds]

17:55 eLobato has joined #ruby-core

18:00 charlies_ has quit [Ping timeout: 252 seconds]

18:02 charliesome has joined #ruby-core

18:06 ZachBeta has quit [Ping timeout: 252 seconds]

18:18 nagachika has quit [Remote host closed the connection]

18:23 nagachika has joined #ruby-core

18:28 samkottler has quit [Ping timeout: 252 seconds]

18:30 Philpax has quit [Read error: Connection reset by peer]

18:33 samkottler has joined #ruby-core

18:39 samkottler has quit [Changing host]

18:39 samkottler has joined #ruby-core

18:41 nagachika has quit [Remote host closed the connection]

18:43 enebo has joined #ruby-core

19:20 ZachBeta has joined #ruby-core

19:36 rafaelfranca has quit [Remote host closed the connection]

19:44 rafaelfranca has joined #ruby-core

19:47 rafaelfranca has quit [Remote host closed the connection]

20:05 heroux has quit [Ping timeout: 264 seconds]

20:07 eLobato has quit [Ping timeout: 248 seconds]

20:10 heroux has joined #ruby-core

20:22 rafaelfranca has joined #ruby-core

20:34 cout is now known as timelord_cout

20:44 someguy has quit [Quit: Page closed]

20:45 eLobato has joined #ruby-core

21:01 rafaelfr_ has joined #ruby-core

21:01 rafaelfranca has quit [Read error: Connection reset by peer]

21:06 eLobato has quit [Ping timeout: 272 seconds]

22:30 shinnya has joined #ruby-core

22:37 ZachBeta has quit [Quit: Computer has gone to sleep.]

22:42 eLobato has joined #ruby-core

23:15 rafaelfr_ has quit [Read error: Connection reset by peer]

23:16 rafaelfranca has joined #ruby-core

23:35 postmodern has joined #ruby-core

23:36 <postmodern> so rubysec is discussing storing ruby implementation advisories in ruby-advisory-db

23:36 <postmodern> with MRI switching to a semver-like versioning scheme

23:36 <postmodern> would it be appropriate to represent older versions in 1.2.3.4 form?

23:47 <drbrain> postmodern: Gem.ruby_version reports patchlevel for releases as a fourth "digit"

23:49 <postmodern> drbrain, ah yes

23:49 <postmodern> drbrain, will probably end up using Gem.ruby_version and Gem::Version

23:50 bffff has joined #ruby-core

23:55 <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 ?

23:56 <drbrain> mpapis: the fourth digit is the patchlevel, so I guess?

23:56 <drbrain> RUBY_PATCHLEVEL

23:57 <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