lucasb has quit [Quit: Connection closed for inactivity]
nirvdrum has quit [Ping timeout: 246 seconds]
sagax has quit [Ping timeout: 252 seconds]
drbobbeaty has joined #jruby
nirvdrum has joined #jruby
rusk has joined #jruby
<kares[m]>
hey! great that tzdata is updated - wanted to do it twice already and I always forgot :)
<kares[m]>
enebo: I do not mind, know ppl hate yanking but I actually welcome the feature
<kares[m]>
what seems to be the issue?
nirvdrum has quit [Ping timeout: 268 seconds]
shellac has joined #jruby
nirvdrum has joined #jruby
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
nirvdrum has quit [Ping timeout: 240 seconds]
nirvdrum has joined #jruby
nirvdrum has quit [Ping timeout: 268 seconds]
<kares[m]>
also should we finish up the jit.time.delta and ship it disabled as an "experimental" feature?
<kares[m]>
the PR should only need to respec and set -1 as a default ...
<kares[m]>
no preference from me - fine to leave it for 9.2.10 (my involvement with the huge Rails app seems to have ended and they did not do any testing with the prepared snapshots as far as I know)
nirvdrum has joined #jruby
nirvdrum has quit [Ping timeout: 268 seconds]
MarcinMielyskiGi has quit [Remote host closed the connection]
liamwhiteGitter[ has quit [Read error: Connection reset by peer]
JesseChavezGitte has quit [Read error: Connection reset by peer]
ThomasEEneboGitt has quit [Read error: Connection reset by peer]
UweKuboschGitter has quit [Remote host closed the connection]
mattpatt[m] has quit [Remote host closed the connection]
KarolBucekGitter has quit [Remote host closed the connection]
headius[m] has quit [Read error: Connection reset by peer]
BlaneDabneyGitte has quit [Read error: Connection reset by peer]
anubhav8421[m] has quit [Remote host closed the connection]
olleolleolle[m] has quit [Remote host closed the connection]
ezzeddine[m] has quit [Remote host closed the connection]
ChrisSeatonGitte has quit [Remote host closed the connection]
cshupp[m] has quit [Remote host closed the connection]
XavierNoriaGitte has quit [Remote host closed the connection]
dsisnero[m] has quit [Read error: Connection reset by peer]
MattPattersonGit has quit [Read error: Connection reset by peer]
RomainManni-Buca has quit [Remote host closed the connection]
lopex[m] has quit [Remote host closed the connection]
OlleJonssonGitte has quit [Remote host closed the connection]
Rumo[m] has quit [Remote host closed the connection]
TimGitter[m]1 has quit [Remote host closed the connection]
JulesIvanicGitte has quit [Remote host closed the connection]
TimGitter[m] has quit [Remote host closed the connection]
voloyev[m] has quit [Remote host closed the connection]
kares[m] has quit [Remote host closed the connection]
FlorianDoubletGi has quit [Read error: Connection reset by peer]
asp_ has quit [Read error: Connection reset by peer]
CharlesOliverNut has quit [Remote host closed the connection]
rdubya[m] has quit [Remote host closed the connection]
enebo[m] has quit [Remote host closed the connection]
nirvdrum has quit [Remote host closed the connection]
nirvdrum has joined #jruby
nirvdrum has quit [Remote host closed the connection]
nirvdrum has joined #jruby
shellac has quit [Quit: Computer has gone to sleep.]
lucasb has joined #jruby
shellac has joined #jruby
subbu|away is now known as subbu
<enebo[m]>
kares: oh that PR has not landed? I thought it had with a default of -1
<kares[m]>
nope it needs a finishing touch
<enebo[m]>
I think we should land on .10 since I would like to try and take a swipe at calibration
<enebo[m]>
but I think we can land it right after.9
<kares[m]>
okay
<kares[m]>
will mark 9.2.10 and add the -1 default
shellac has quit [Quit: Computer has gone to sleep.]
shellac has joined #jruby
<enebo[m]>
kares: thanks. Sorry that one got lost. I was frustrated in not cracking the calibration nut
<enebo[m]>
I also wanted some back edge heuristic so a heavy loop method which is called less can still JIT
<enebo[m]>
but my main problem overall is not being able to measure what we JIT vs what we don't today and understand which important methods were missed (if any)
<enebo[m]>
This last point is probably the biggest grey area.
xardion has quit [Remote host closed the connection]
<enebo[m]>
updated 2.5.3 -> 2.5.7 and new rubygems release
<headius[m]>
2.5.3?
enebo has quit [Read error: Connection reset by peer]
enebo has joined #jruby
enebo has quit [Read error: Connection reset by peer]
enebo has joined #jruby
<enebo[m]>
we have decided to long form the release notes and try and put a little more effort into them
<enebo[m]>
Ruby version we support
<headius[m]>
I'm almost done with this
<enebo[m]>
jruby 9.2.9.0-SNAPSHOT (2.5.7) 2019-10-25 0a03916 Java HotSpot(TM) 64-Bit Server VM 25.172-b11 on 1.8.0_172-b11 +jit [linux-x86_64]
<headius[m]>
oh right stdlib
<headius[m]>
2.5.7
<enebo[m]>
in practice it may be only stdlib files but in theory it should mean anything in core which was fixed we should consider a bug now
<headius[m]>
also added RG
<enebo>
cool
<headius[m]>
yeah agreed
<headius[m]>
I'm happy to do this job each release but this is why I thought we might want to have a rolling wiki page or issue where we can all insert sections as we work on things
<headius[m]>
last past of issues/PRs now
<enebo>
and I am not adverse to doing this either but we just should get into some groove here planning wise
<enebo>
as you say we can pre-seed what will be in the release notes by adding to a page so this is not as big an activity
<headius[m]>
Ok done
<headius[m]>
order is totally negotiable...process wait is probably not the most important thing but it was first in the issue list
<headius[m]>
I'm also not in love with just listing the issue number, but if we have the full list below I think people can cross-reference
<enebo>
yeah I think it can be useful in case and not in others
<enebo>
cases
<enebo>
I will reorder a little bit quick
<headius[m]>
it's not like they have to dig through hundreds to find the one they are interested in...I just wanted to localize some of them with better descriptions
<enebo>
well sometimes the title is not obvious so it can be helpful
<headius[m]>
last section after this would be the aggregate "## Issues and PRs closed# with the full list you generate
enebo has quit [Read error: Connection reset by peer]
<headius[m]>
and whatever copy you want up front I don't care
<headius[m]>
I think people will appreciate this breakdown of the larger items
<headius[m]>
anyone with a single pet issue can still find theirs in the list too
nirvdrum has joined #jruby
enebo has joined #jruby
<enebo[m]>
yeah
enebo has quit [Read error: Connection reset by peer]
enebo has joined #jruby
enebo has quit [Read error: Connection reset by peer]
nirvdrum has quit [Ping timeout: 240 seconds]
lucasb has quit [Quit: Connection closed for inactivity]
donv[m] has joined #jruby
<donv[m]>
Woohoo! Hi!
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<headius[m]>
donv: welcome!
<headius[m]>
donv: I use the Riot electron app btw, and I think enebo is using a Pidgin plugin
<headius[m]>
maybe not
<headius[m]>
I haven't tried any other clients because Riot seems 👍
<headius[m]>
@kare
<headius[m]>
ugh
<headius[m]>
I am still not used to how Riot does mentions
<headius[m]>
kares: I did include a link to your classloader work under memory improvements
<headius[m]>
enebo and I were chatting about how to keep some rolling release notes, and it seems like the best way would be to set up a prerelease wiki page during development
<headius[m]>
I'll create one for JRuby 9.2.10 now
snickers has joined #jruby
<lopex>
wow, that websocket/puma issue is fixed on 9.2.9
snickers has quit [Read error: Connection reset by peer]