I will use the holidays to do my first real steps with Rails. No toying around but actually developing an application that is planned to be used in an production environment early next year. Now I have read several times that 1.8.3 seems to have some bugs, that are causing people to stick too 1.8.2. Sadly, I don't come up with the right google mantra to find anything helpful concerning this question. So, I like to ask here if someone can give me some pointers concering this. Or otherwise disperse the bad feeling I have at the moment.
So far, I haven't discovered any bug myself and I already use 1.8.3 for some production code. Mostly scripts for workflow jobs so far. May be using Rails it is more an issue.
Hopefully, I am not wasting your time and bandwidth, cause I could have found all the information I need in an obvious location.
On Monday 19 December 2005 01:27 pm, James Edward Gray II wrote:
On Dec 19, 2005, at 12:22 PM, Oliver Andrich wrote:
> So, I like to ask here if someone can give me some pointers
> concering this. Or otherwise disperse the bad feeling I have at
> the moment.
You're probably fine. 1.8.3 originally broke Rails (and Rake, I
believe) but the latest versions work fine.
The biggest outstanding 1.8.3 bug is the you can't effectively
build RubyGems with it. Just be aware of that.
1.8.4 is due in less than a week now as well, just FYI.
Pretty much, yes. But since RubyForge is currently running < 1.8.3, you have the consider that it's not possible to distribute anything made with the newer versions (through them).
Just to be clear, this is a YAML issue (not RubyGems).
James Edward Gray II
···
On Dec 19, 2005, at 1:07 PM, gabriele renzi wrote:
James Edward Gray II ha scritto:
The biggest outstanding 1.8.3 bug is the you can't effectively build RubyGems with it. Just be aware of that.
was'nt the problem about using gems made with ruby-X with ruby-Y ?
Many thanks for the information. This gives me a much better feeling for the things ahead.
Best regards,
Oliver
James Edward Gray II schrieb:
···
On Dec 19, 2005, at 1:07 PM, gabriele renzi wrote:
James Edward Gray II ha scritto:
The biggest outstanding 1.8.3 bug is the you can't effectively build RubyGems with it. Just be aware of that.
was'nt the problem about using gems made with ruby-X with ruby-Y ?
Pretty much, yes. But since RubyForge is currently running < 1.8.3, you have the consider that it's not possible to distribute anything made with the newer versions (through them).
Just to be clear, this is a YAML issue (not RubyGems).
