<GitHub175>
[opal-jquery] adambeynon tagged v0.1.1 at eac7d1b: http://git.io/qxOf_Q
GitHub34 has joined #opal
GitHub34 has left #opal [#opal]
<GitHub34>
opal-jquery/master 61249ed Adam Beynon: v0.1.1
<GitHub34>
[opal-jquery] adambeynon pushed 2 new commits to master: http://git.io/RkdHJw
<GitHub34>
opal-jquery/master bafd14a Adam Beynon: HTTP requires native
GitHub153 has joined #opal
<GitHub153>
[opalrb.org] adambeynon pushed 1 new commit to master: http://git.io/0TMGlg
<GitHub153>
opalrb.org/master 3562fe0 Adam Beynon: Update to opal 0.5.1
GitHub153 has left #opal [#opal]
elia has quit [Quit: Computer has gone to sleep.]
[spoiler] has joined #opal
elia has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #opal
<elia>
adambeynon, hey there!
<adambeynon>
elia: morning!
<elia>
saw the twitter buzz post preso? :)
<elia>
adambeynon, I would like to talk about the 0.5.1 vs. 0.6 relese…
<adambeynon>
yeh, definitely some good reaction to it
<adambeynon>
still waiting for confreaks to upload the video..
<elia>
adambeynon, yeah, I think it'll come up during nov
<adambeynon>
hopefully
<adambeynon>
elia: what are your thoughts on the releases then
<elia>
adambeynon, about the version i'm ok with whatever line you choose to keep, but if it's to break in tiny release I need to know and use a hard version requirement inside opal-rails and projects
<elia>
just this :)
<elia>
(by tiny I mean x in 0.0.x)
pickdenis has quit [Ping timeout: 250 seconds]
<adambeynon>
yes, fair enough
<adambeynon>
I had meant to require native back inside corelib for the release
<elia>
adambeynon, thought of that too as a solution
<adambeynon>
elia: meh did mention somehting about a change inside native, but I cant see many differences on master
<elia>
adambeynon, i remember breaking changes too, lemme check
<elia>
adambeynon, I think it's that he switched to module Native / class Native::Object
<elia>
(from: module Native::Base / class Native)
<adambeynon>
ughh, Im really not a fan of the Native stuff
<elia>
adambeynon, :)
<elia>
adambeynon, as a side note I must say I changed my mind on which is better, I'm know quite ok with module Native
<elia>
adambeynon, said that it remains a breaking change :)
<adambeynon>
yeah, that part I agree with
<adambeynon>
yes
<adambeynon>
I didnt realise how much had changed actually
<adambeynon>
Im suspecting that a gem-yank might be in order here
<elia>
adambeynon, yanking 0.5 and 0.5.1 is another viable solution, not a very gentle one, but at least there wouldn't be any version confusion
<elia>
ahha
<adambeynon>
^^ indeed :)
<elia>
*haha
<adambeynon>
so, 0.5 had the old native stuff yeh?
<elia>
yes
<adambeynon>
right, so I think keep 0.5, yank 0.5.1 and keep the new native stuff in a branch to merge in later
<elia>
adambeynon, btw the changelog becomes more and more a daunting task… :D
<adambeynon>
elia: I know :( lol
<elia>
adambeynon, fine, unless you want to yank 0.5.0…
<elia>
…nay
<elia>
nvm
<elia>
I didn't liked the idea of branches like that before 1.0
<elia>
but your sol makes much more sense
<adambeynon>
I might also have to push out 0.5.2 (or something) at the same time, rspec needs some post 0.5.0 stuff
<adambeynon>
well, for mocks it does
<elia>
adambeynon, np, bugfix releases are always welcomed :D
<adambeynon>
:D might need to speak with meh though - 0.6.0 might be a little way off, so I dont know how hes going to work off the older Native stuff
<elia>
adambeynon, yeah, this stuff needs to sorted out
<elia>
adambeynon, you thinking of any particular feat for 0.6 or just don't want it to be too close to 0.5?
meh` has joined #opal
<elia>
adambeynon, what about a 0-5-stable bugfix only brach, and master headed towards 0.6?
<meh`>
I don't see the problem with releasing something after such a short time
<meh`>
and having multiple branches is a gargantuan pain in the ass
<elia>
meh`, me too, but I think adam prefers to have some more stuff before it, in that case I'd prefer a 0.5 suport brach and normal development inside master
<elia>
that would be mostly a dead branch, there just if there's blocking / urgent stuff that's needed by other libs, I think…
<meh`>
I don't really see the problem, 0.x versions are supposed to change anytime
<elia>
meh`, just to be clear, I think too the branch is a PITA and should be avoided, but it's better that than breaking the shifted semver we agreed to use before 1.0
<meh`>
even having breaking changes in 0.x.y is semver
<meh`>
that's what the 0.x is for
<meh`>
and yes, you should have hard dependencies, not ~>
<meh`>
at least until we hit 1.0
<elia>
meh`, yeah, I know semver allows for anything before 1.0, but it also allows us to pick a rule of our own
<elia>
I'm all for this shifted semver-like system, it just makes easier to manage version requirements inside libs
<elia>
otherwise I need to switch to require precise versions inside gemspec
DouweM has quit [Ping timeout: 260 seconds]
<meh`>
it's just development is already slow, if I have to backport the patches myself it's going to be even slower
<meh`>
and if it's adam that has to do it, then he can't focus on the important stuff
<elia>
meh`, ok, we could also simply yank 0.5.0, and move on
<meh`>
that too
<meh`>
I'd rather do that
<meh`>
I think 0.5 was hastened
<elia>
codename: rubyconf
DouweM has joined #opal
DouweM has quit [Read error: Connection reset by peer]