gmane.comp.java.netbeans.modules.ruby.devel

Is a JRuby 1.1.3 upgrade planned?

JRuby 1.1.3 will be out soon (end of week, maybe later, but certainly 
well before NB 6.5 :o)

Any plans to upgrade to this and when?

-Peter

headers

Martin Krauskopf | 15 Jul 23:17

Re: Is a JRuby 1.1.3 upgrade planned?

Peter Williams wrote:
> JRuby 1.1.3 will be out soon (end of week, maybe later, but certainly 
> well before NB 6.5 :o)
> 
> Any plans to upgrade to this and when?

Surely it is. This is usually done by Tor, since he need to tweak 
JRuby's lexer and parser so he does it all at once.
Usually done immediately after new release is out. If not somebody will 
file a bug soon ;)

	m.

headers

Tor Norbye | 16 Jul 07:02

Re: Is a JRuby 1.1.3 upgrade planned?

On Jul 15, 2008, at 2:17 PM, Martin Krauskopf wrote:

> Peter Williams wrote:
>> JRuby 1.1.3 will be out soon (end of week, maybe later, but  
>> certainly well before NB 6.5 :o)
>> Any plans to upgrade to this and when?
>
> Surely it is. This is usually done by Tor, since he need to tweak  
> JRuby's lexer and parser so he does it all at once.
> Usually done immediately after new release is out. If not somebody  
> will file a bug soon ;)

Yep, I'll upgrade us as soon as it's released.

-- Tor

headers

Tor Norbye | 21 Jul 06:24

Re: Is a JRuby 1.1.3 upgrade planned?

On Jul 15, 2008, at 10:02 PM, Tor Norbye wrote:

> On Jul 15, 2008, at 2:17 PM, Martin Krauskopf wrote:
>
>> Peter Williams wrote:
>>> JRuby 1.1.3 will be out soon (end of week, maybe later, but  
>>> certainly well before NB 6.5 :o)
>>> Any plans to upgrade to this and when?
>>
>> Surely it is. This is usually done by Tor, since he need to tweak  
>> JRuby's lexer and parser so he does it all at once.
>> Usually done immediately after new release is out. If not somebody  
>> will file a bug soon ;)
>
> Yep, I'll upgrade us as soon as it's released.

Just did it -- changeset bbc2416e049e, included in build #2941 and  
later.

-- Tor

headers

Peter Williams | 21 Jul 19:19

Re: Is a JRuby 1.1.3 upgrade planned?

Saw that last night, thanks Tor.

Does this mean things are now stable enough that JRuby upgrades are 
pretty painless now?  I remember that upgrading to 1.1.2 took a few weeks.

-Peter

Tor Norbye wrote:
> On Jul 15, 2008, at 10:02 PM, Tor Norbye wrote:
>
>> On Jul 15, 2008, at 2:17 PM, Martin Krauskopf wrote:
>>
>>> Peter Williams wrote:
>>>> JRuby 1.1.3 will be out soon (end of week, maybe later, but 
>>>> certainly well before NB 6.5 :o)
>>>> Any plans to upgrade to this and when?
>>>
>>> Surely it is. This is usually done by Tor, since he need to tweak 
>>> JRuby's lexer and parser so he does it all at once.
>>> Usually done immediately after new release is out. If not somebody 
>>> will file a bug soon ;)
>>
>> Yep, I'll upgrade us as soon as it's released.
>
> Just did it -- changeset bbc2416e049e, included in build #2941 and later.
>
> -- Tor
>
>
>

(Continue reading)

headers

Tor Norbye | 21 Jul 20:51

Re: Is a JRuby 1.1.3 upgrade planned?

On Jul 21, 2008, at 10:19 AM, Peter Williams wrote:

> Saw that last night, thanks Tor.
>
> Does this mean things are now stable enough that JRuby upgrades are  
> pretty painless now?

Yes, this was easy. It all depends on what kinds of changes they make.  
Whenever they change the parse tree layout (adding new logical types  
etc.) that affects a lot of our code but this time the changes were  
trivial.

-- Tor

headers

Chris Kutler | 21 Jul 17:42

Re: Is a JRuby 1.1.3 upgrade planned?

Is this the respin that they did over the weekend with the warbler fix?

Tor Norbye wrote:
> On Jul 15, 2008, at 10:02 PM, Tor Norbye wrote:
>
>> On Jul 15, 2008, at 2:17 PM, Martin Krauskopf wrote:
>>
>>> Peter Williams wrote:
>>>> JRuby 1.1.3 will be out soon (end of week, maybe later, but 
>>>> certainly well before NB 6.5 :o)
>>>> Any plans to upgrade to this and when?
>>>
>>> Surely it is. This is usually done by Tor, since he need to tweak 
>>> JRuby's lexer and parser so he does it all at once.
>>> Usually done immediately after new release is out. If not somebody 
>>> will file a bug soon ;)
>>
>> Yep, I'll upgrade us as soon as it's released.
>
> Just did it -- changeset bbc2416e049e, included in build #2941 and later.
>
> -- Tor
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

(Continue reading)

headers

Tor Norbye | 21 Jul 20:52

Re: Is a JRuby 1.1.3 upgrade planned?

On Jul 21, 2008, at 8:42 AM, Chris Kutler wrote:

> Is this the respin that they did over the weekend with the warbler  
> fix?

What Warbler fix? I never saw any notes about that. I grabbed the bits  
on Friday night so I probably don't have it - but if they've made  
critical fixes since 1.1.3 they ought to release a 1.1.4 ...

-- Tor

headers

Chris Kutler | 21 Jul 21:09

Re: Is a JRuby 1.1.3 upgrade planned?

I copied below the 7/20 email that in the user@...
alias 
with subject of Re: [jruby-user] 1.1.3 Warbler rake gem error:

> Charles Oliver Nutter wrote:
>> Mike Herrick wrote:
>>> That or maybe Warbler could fix it up somehow.
>>>
>>> Pretty easy work around, but yeah - everyone basically uses Warbler 
>>> now so it will happen a lot and might scare the brand-newbs.
>>
>> I think I'm going to make an executive decision and push out a new 
>> bin dist that includes the gem files. It's going to mess up too many 
>> people.
>
> I've pushed new dists to the server for this. Since it's still the 
> weekend, I think we're ok just replacing what's there. I've also 
> updated the 1_1_3 tag and trunk.
>
> Mike: Can you grab it and confirm it's working?
>
> All: Because we only have so many hands here, perhaps we should plan 
> on always doing a release of the dists a day or two before we announce 
> it, so those of you trying things out can test it before we tell the 
> world? Or we push out an RC each time before the main release? 
> Obviously we'd like to avoid this dist-juggling every time.
>
> - Charlie 

Tor Norbye wrote:

(Continue reading)

headers

Tor Norbye | 21 Jul 22:29

Re: Is a JRuby 1.1.3 upgrade planned?

Thanks for the heads-up. Those bits are not included in our bundle. I  
guess we should grab another one. Ugh.

-- Tor

On Jul 21, 2008, at 12:09 PM, Chris Kutler wrote:

> I copied below the 7/20 email that in the user@...  
> alias with subject of Re: [jruby-user] 1.1.3 Warbler rake gem error:
>
>
>> Charles Oliver Nutter wrote:
>>> Mike Herrick wrote:
>>>> That or maybe Warbler could fix it up somehow.
>>>>
>>>> Pretty easy work around, but yeah - everyone basically uses  
>>>> Warbler now so it will happen a lot and might scare the brand- 
>>>> newbs.
>>>
>>> I think I'm going to make an executive decision and push out a new  
>>> bin dist that includes the gem files. It's going to mess up too  
>>> many people.
>>
>> I've pushed new dists to the server for this. Since it's still the  
>> weekend, I think we're ok just replacing what's there. I've also  
>> updated the 1_1_3 tag and trunk.
>>
>> Mike: Can you grab it and confirm it's working?
>>
>> All: Because we only have so many hands here, perhaps we should

(Continue reading)

headers

Tor Norbye | 22 Jul 00:53

Re: Is a JRuby 1.1.3 upgrade planned?

Ok, we have the latest version now (changeset abb3f99664ac). Thanks  
for the pointer Chris.  By the way Martin, this fixes the failing ruby  
platform unit test so I removed the comment again.

-- Tor

On Jul 21, 2008, at 1:29 PM, Tor Norbye wrote:

> Thanks for the heads-up. Those bits are not included in our bundle.  
> I guess we should grab another one. Ugh.
>
> -- Tor
>
> On Jul 21, 2008, at 12:09 PM, Chris Kutler wrote:
>
>> I copied below the 7/20 email that in the user@...  
>> alias with subject of Re: [jruby-user] 1.1.3 Warbler rake gem error:
>>
>>
>>> Charles Oliver Nutter wrote:
>>>> Mike Herrick wrote:
>>>>> That or maybe Warbler could fix it up somehow.
>>>>>
>>>>> Pretty easy work around, but yeah - everyone basically uses  
>>>>> Warbler now so it will happen a lot and might scare the brand- 
>>>>> newbs.
>>>>
>>>> I think I'm going to make an executive decision and push out a  
>>>> new bin dist that includes the gem files. It's going to mess up  
>>>> too many people.

(Continue reading)