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
shinnya has joined #ruby-core
nagachika has joined #ruby-core
nagachik_ has joined #ruby-core
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
shinnya has quit [Ping timeout: 246 seconds]
nagachik_ has joined #ruby-core
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
nagachik_ has joined #ruby-core
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
tylersmith has quit [Remote host closed the connection]
nagachik_ has joined #ruby-core
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
hsbt has quit [Ping timeout: 265 seconds]
nagachik_ has joined #ruby-core
heroux has quit [Ping timeout: 264 seconds]
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
heroux has joined #ruby-core
hsbt has joined #ruby-core
nagachika has joined #ruby-core
<zzak>
soraher: i am confirming reschedule of conference room for thursday
nagachik_ has joined #ruby-core
<soraher>
zzak: Sorry we can't provide place on Thursday, Just checked meeting rooms availability, there's no room available
hsbt has quit [Quit: Tiarra 0.1+svn-39209: SIGTERM received; exit]
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
<zzak>
:(
hsbt has joined #ruby-core
<soraher>
zzak: rails tokyo meetup held on thursday, our HR team seems locked nearby meeting rooms. If attendees can accept loud environment, we can provide there
<soraher>
zzak: but room already booked for Friday has blocked with another schedule on Thursday, so we provide smaller room (6 or 7 people) if we change the schedule for Thursday
<zzak>
hmm
<zzak>
our option is:
<zzak>
* small meeting room thursday (6-7 people) at cookpad
<zzak>
* bigger meeting room friday (8-10 people) at cookpad
<zzak>
also, we can reserve conferences rooms for both days
<zzak>
whatever we dont cover with matz on thursday, we can discuss on friday
<zzak>
matz can only go thursday
nagachik_ has joined #ruby-core
nagachik_ has quit [Remote host closed the connection]
<zzak>
can someone ping shyouhei and yugui about either day?
nagachik_ has joined #ruby-core
nagachika has quit [Read error: Connection reset by peer]
<hsbt>
I think thursday meeting is suddenly. If we couldn't invite key person, we shouldn't decide important things.
<zzak>
hsbt: agree, agenda depends on attendance
tylersmith has joined #ruby-core
tylersmith has quit [Ping timeout: 240 seconds]
<znz_jp>
biff: [ruby-changes:31877] charliesome:r43956 (trunk): * variable.c (rb_mod_constants): when calling Module#constants with - http://mla.n-z.jp/?ruby-changes=31877
nagachika has joined #ruby-core
nagachika has quit [Remote host closed the connection]
nagachik_ has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
knu has quit [Ping timeout: 264 seconds]
nagachik_ has joined #ruby-core
nagachik_ has quit [Remote host closed the connection]
nagachika has quit [Read error: Connection reset by peer]
nagachika has joined #ruby-core
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
nari has quit [Ping timeout: 264 seconds]
nagachika has quit [Remote host closed the connection]
nagachik_ has joined #ruby-core
nagachik_ has quit [Ping timeout: 260 seconds]
charliesome has joined #ruby-core
<zzak>
hsbt: did you resolve the issue with travis autodeploy?
knu has joined #ruby-core
nagachika has joined #ruby-core
nagachika has quit [Remote host closed the connection]
<hsbt>
not resolved
nurse has quit [Quit: Quit Nadoka 0.8.5+git(v0.8.4-13-gf69f8ce-dt)]
Glass_saga has quit [Ping timeout: 240 seconds]
ggherdov has quit [Ping timeout: 240 seconds]
epitron has quit [Ping timeout: 240 seconds]
epitron has joined #ruby-core
ggherdov has joined #ruby-core
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
charliesome has joined #ruby-core
rafaelfranca has quit [Remote host closed the connection]
nagachika has joined #ruby-core
nagachik_ has joined #ruby-core
nagachi__ has joined #ruby-core
<znz_jp>
biff: [ruby-changes:31878] glass:r43957 (trunk): * hash.c (rb_hash_rehash): make temporary st_table under the control - http://mla.n-z.jp/?ruby-changes=31878
nagachika has quit [Ping timeout: 248 seconds]
nagachi__ has quit [Ping timeout: 272 seconds]
charliesome has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<znz_jp>
biff: [ruby-changes:31879] usa:r43958 (trunk): * hash.c (getenv): fixed test failures introduced by r43950. - http://mla.n-z.jp/?ruby-changes=31879
<hone>
like you can't use tool/merger.rb in ruby 1.8.7/1.9.2
<hone>
it was added in ruby 1.9.3
<drbrain>
you can backport it!
<hone>
!
<hone>
should I backport it?
<drbrain>
if it makes your life as a committer easier, yes
<drbrain>
I follow the "Always build outside of $(srcdir)" method
<drbrain>
so I have ruby/trunk and ruby/build, ruby/branches/ruby_2_0_0 and ruby/build_2_0
<drbrain>
then I make my changes in ruby/trunk (since I'm not a branch maintainer)
<drbrain>
and run: make all test-all TESTS=-j12
<samkottler>
zzak: most of the major items are covered, but it's worth noting that RHEL is still on 1.8.7. I'd be maintaining 1.9.2 individually for the short term.
<drbrain>
from build
<samkottler>
1.9.3 is where we'll want a longer support period
<drbrain>
then: make change
eLobato has joined #ruby-core
<drbrain>
edit changelog.txt (in build/) and use it to update ChangeLog (in trunk/)
<drbrain>
err, change.log, not changelog.txt
<drbrain>
then, to commit svn ci -F ../build/change.log
tylersmith has quit [Read error: Connection reset by peer]