ddfreyne changed the topic of #nanoc to: 3.6.8 (mar 22th) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
alerante has quit [Remote host closed the connection]
VitamineD has quit [Quit: Leaving.]
alerante has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
relix has joined #nanoc
<travis-ci> [travis-ci] nanoc/nanoc/bug/fix-jruby-failures ec1b0c2 Denis Defreyne: The build failed.
<travis-ci> [travis-ci] nanoc/nanoc/release-3.6.x afc8434 Denis Defreyne: The build passed.
achal has joined #nanoc
<guardian> o/
irsol has quit [Ping timeout: 245 seconds]
francois2 has quit [Ping timeout: 240 seconds]
francois2 has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
cDlm has joined #nanoc
irsol has joined #nanoc
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
alerante has joined #nanoc
<guardian> ddfreyne: could #412 land in 3.6.9?
relix has joined #nanoc
timgauthier has joined #nanoc
timgauthier has left #nanoc [#nanoc]
jugglinmike has joined #nanoc
cDlm has quit [Ping timeout: 252 seconds]
<guardian> re
<ddfreyne> guardian: Since #412 is not a bug fix, no. It's already in master and it'll be part of 3.7.0
<ddfreyne> (You can point your Gemfile to use the nanoc/nanoc GitHub repository if you want to)
<ddfreyne> A 3.7 release should not be too far away. Probably next month, or even this month.
<ddfreyne> 3.6.9 hopefully this week.
<guardian> hmm
<ddfreyne> Jeez, my release cycle is slow. 3.6.0 was released 14 months ago.
<guardian> no feature in a point release?
<ddfreyne> guardian: Nope
cDlm has joined #nanoc
<ddfreyne> I follow http://semver.org/
<ddfreyne> “Given a version number MAJOR.MINOR.PATCH, increment the: […] MINOR version when you add functionality in a backwards-compatible manner”
<bobthecow> ddfreyne: :shipit:
<bobthecow> 3.7.0!
<ddfreyne> I want to fix a bunch of JRuby errors and ship 3.6.9 first though
<ddfreyne> I don't know where those JRuby issues came from. I knew the JRuby build was flaky, but I did not remember having a dozen failures/errors.
<guardian> #412 is backward-compatible, in fact #419 and #420 also are
<ddfreyne> guardian: Yup, but adding new features still means incrementing the minor version number
<guardian> ok
<ddfreyne> guardian: Hence, #412, #419 and #420 cannot go into 3.6.x
<guardian> ok
<guardian> too bad, I guess I'll go with a VM where nanoc is preinstalled from source then
<ddfreyne> guardian: Do you use Bundler? (You should)
<guardian> I do
<guardian> what does that change?
<ddfreyne> You can say this: gem 'nanoc', github: 'nanoc/nanoc'
<guardian> ah...
<ddfreyne> A `bundle install` will then fetch it from the GitHub master branch
<guardian> so I can use my fork instead?
<guardian> interesting
<ddfreyne> You can, and you can even use the main master branch
<guardian> only if #419 and #420 land :)
<guardian> nice I learnt something today
<ddfreyne> I will review them more closely soon
<ddfreyne> My main focus at the moment is getting rid of the JRuby failures
<guardian> ok
alerante has quit [Remote host closed the connection]
achal has quit [Quit: Connection closed for inactivity]
<travis-ci> [travis-ci] nanoc/nanoc/master 2d12999 Denis Defreyne: The build passed.
achal has joined #nanoc
<travis-ci> [travis-ci] nanoc/nanoc/bug/fix-jruby-failures 5d6645a Denis Defreyne: The build has errored.
irsol has quit [Ping timeout: 240 seconds]
<ddfreyne> Ugh, I think Nokogiri on JRuby is broken.
<ddfreyne> I have test cases where the output significantly differs between MRI-Nokogiri and JRuby-Nokogiri
<guardian> https://github.com/sparklemotion/nokogiri/wiki/Pure-Java-Nokogiri-for-JRuby "Pure Java version of Nokogiri is a Java port for JRuby. When Nokogiri 1.5.x is used on JRuby, pure Java version starts working on it."
<guardian> sounds all downhill :)
<guardian> meant uphill
<ddfreyne> I even have a test case where I have an XSL stylesheet that parses on MRI-Nokogiri and fails on JRuby-Nokogiri
<ddfreyne> I might have to start reporting bugs.
<ddfreyne> guardian: Yeah, not stuff you want to be doing on a monday evening at 9.30 PM, heh
<ddfreyne> Anyway, just trying.
<guardian> there are 172 open issues
<guardian> good luck
<guardian> :/
<ddfreyne> There's no good alternatives though.
<ddfreyne> REXML maybe, but it's awfully slow.
<travis-ci> [travis-ci] nanoc/nanoc/bug/fix-jruby-failures 771c56a Denis Defreyne: The build is still failing.
irsol has joined #nanoc
<ddfreyne> I could start using this: https://github.com/ohler55/ox
<guardian> indeed
<ddfreyne> Works on JRuby too.
alerante has joined #nanoc
<bobthecow> ddfreyne: it doesn't have as much functionality as nokogiri though, so you'd have to check what you're using and see if Ox supports all of it.
alerante has quit [Ping timeout: 240 seconds]
<ddfreyne> Yeah.
<ddfreyne> But seriously:
<ddfreyne> I’m done now.
<cDlm> shotgun issue reporting ?
<ddfreyne> All of those issues appear in the nanoc test cases.
<travis-ci> [travis-ci] nanoc/nanoc/bug/fix-jruby-failures 639e308 Denis Defreyne: The build is still failing.
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
achal has quit [Quit: Connection closed for inactivity]
jugglinmike has quit [Quit: Leaving.]
alerante has joined #nanoc
FunkyPenguin has quit [Ping timeout: 276 seconds]
FunkyPenguin has joined #nanoc