breakingthings has quit [Ping timeout: 246 seconds]
breakingthings has joined #rom-rb
namelessjon has quit [Ping timeout: 246 seconds]
namelessjon has joined #rom-rb
jgaskins has quit [Ping timeout: 246 seconds]
jgaskins has joined #rom-rb
CraigBuchek has joined #rom-rb
mkristian has joined #rom-rb
bf4 has joined #rom-rb
snusnu1 has joined #rom-rb
snusnu has quit [Ping timeout: 246 seconds]
snusnu1 has quit [Client Quit]
snusnu has joined #rom-rb
mkristian_ has joined #rom-rb
mkristian has quit [Ping timeout: 272 seconds]
lfox has joined #rom-rb
vsorlov has joined #rom-rb
mkristian__ has joined #rom-rb
mkristian_ has quit [Ping timeout: 272 seconds]
mkristian_ has joined #rom-rb
mkristian__ has quit [Ping timeout: 248 seconds]
snusnu has quit [Quit: Leaving.]
snusnu has joined #rom-rb
mbj has joined #rom-rb
<mbj>
dkubb, snusnu: Hola.
<snusnu>
mbj: yo
<snusnu>
mbj: i've quickly skimmed over the 1.8 debate, i've no strong opinion, apart from the *condition* from my side, that i will never ever again, repeat *never ever again* fix any code for 1.8 compat
<snusnu>
if someone else (sferik) wants to manage that, i'm fine with it .. i will certainly not run any tests on 1.8 tho, for any gem related to rom
<snusnu>
and i will not fix breakage i may have introduced
<snusnu>
mbj: to iterate on the no strong opinion, sorry if that may sound rude, but i'm not at all interested in thinking up solutions even
<snusnu>
dkubb: ^^
lfox has quit [Quit: ZZZzzz…]
Eiam has joined #rom-rb
dkubb|away has joined #rom-rb
<dkubb|away>
snusnu: yeah, I'm trying to think of a solution that'll work like that
<dkubb|away>
snusnu: one solution I have is to release the support gems like equalizer as 1.0 and 2.0 .. the 1.0 would retain 1.8 compat, while 2.0 would be 1.9.3+ .. I would maintain the 2.0 gems in the master branch, and someone else would backport to the ruby-1.8.7 branch and release the 1.x gems from there
<snusnu>
dkubb: yeah, imo that should be guaranteed, no dev impact on any of us (well, i can only talk about me of course)
<snusnu>
dkubb: that might work yeah, but (again sorry), as i already said, i don't even wanna spend brain cycles on what might or might not work
<dkubb|away>
no worries
<snusnu>
1.8 is dead as it should be, if people need it, they should take care of it
dkubb has quit [Ping timeout: 252 seconds]
dkubb|away is now known as dkubb
<dkubb>
snusnu: no worries, I also don't want to spend too much time. I'm just trying to help someone out with their problem.
<snusnu>
dkubb: yeah, i totally respect that
<snusnu>
dkubb: i just wanted to drop my 2cents as mbj pinged me about it recently
<snusnu>
dkubb: i got sick during the weekend tho, hence i'm lagging behind a bit
<dkubb>
that sucks
<dkubb>
I always get sick on boxing day, so I'm just waiting for that
<snusnu>
heh, don't think about it too much, self fulfilling prophecies u know … ;)
<dkubb>
heh, it's been the same for years. I don't get it
<snusnu>
damnit
<dkubb>
I have this theory that stress keeps me healthy, and then when the stress lets up after Christmas, then my body relaxes and I get sick
lfox has joined #rom-rb
<snusnu>
i've heard many people say that already, and i've actually seen a lot of people "behaving" like that too
<snusnu>
work, healthy, holiday, sick
<snusnu>
sad thing
<dkubb>
I love Christmas, but it's also a really busy time of year
<snusnu>
...
<snusnu>
yeah
<snusnu>
so, fingers crossed you'll break your rule this year ;)
<dkubb>
haha, I hope so
breakingthings has quit []
mkristian__ has joined #rom-rb
mkristian_ has quit [Ping timeout: 272 seconds]
jgaskins has quit [Quit: Leaving]
<mbj>
dkubb: I like that versioning idea!
<mbj>
dkubb: So lets to better: 0.x.x is 1.8 while 1.x.x is >= 1.9
<mbj>
dkubb: Its time we move all this stuff to 1.x
<dkubb>
mbj: yeah, then we can use strong ruby versions in the gemspec and then just tell people to specify their versions to select the best one
<dkubb>
that's a good idea actually
<mbj>
dkubb: So actually dont "cheat"
<dkubb>
then it'll be clear that the 1.8 stuff is on it's way out
<mbj>
dkubb: I'd totally support this.
<mbj>
dkubb: Nice. I think this will work.
<dkubb>
we could have it so 0.9 is 1.8.7, and 1.0 is 1.9.3 (or maybe 2.0)
<mbj>
dkubb: We'll ask sferik to work on that 0.9 branches
<mbj>
dkubb: And we could add him as owner to rubygems, as long he never pushes anything in the 1.0 version space, we'll never notice!
<dkubb>
yeah, 0.9 may lag a bit, but that' ok
<mbj>
dkubb: And if someone complains about his 0.9 work, we'll say, look at the 1.x version the newest version ;)
<dkubb>
other gems, like spree, often maintain several generations of rubygems, and stuff is committed to master first and then backported
<mbj>
Yeah
<mbj>
But directly go to 2.0 for post 18 is IMHO not needed.
<mbj>
That 0 in front of the 1.8 versions is also a good sign ;)
<mbj>
dkubb, snusnu: Should we ack in this idea and tell sferik?
<dkubb>
mbj: the rule will probably be that all commits happen on master, and *only* 1.8 specific compatibility commits happen in the 0-9-stable branch
<mbj>
dkubb: yeah
<mbj>
devtools does not need to be ported at all.
mkristian_ has joined #rom-rb
<dkubb>
both versions must be api compatible so that upgrading between them is seamless
<dkubb>
tis policy will also ensure they have the same specs, other than maybe small syntax differences
<mbj>
dkubb: Yeah, but as we officiall do not support 0.9 I'd not be angry if 0.9 breaks like hell (even while I trust sferik to do his job well).
<dkubb>
I'm sure it will if we use travis
<dkubb>
0.9 will just lag a bit, that's all
<mbj>
dkubb: I'd just push this solution. snsnusnu already agreed as "not interested", I think solnic will also.
<dkubb>
I'd still have the same level of quality requirements
<mbj>
No need to delay a decision. To finish this discussion.