Sven:

I don't think the first release of ChiliProject will completely support Ruby 1.9 but I really want to get 2.0 to work with it. Depending on what changes we need to support Ruby 1.9, we might be able to add support to a later minor release of ChiliProject before 2.0 (e.g. 1.2.0, 1.3.0).

The big thing is we need people to start trying ChiliProject out with 1.9 and reporting any bugs they find.

Eric Davis

The big thing is we need people to start trying ChiliProject out with 1.9 and reporting any bugs they find.

Count me in. Are there any resources to find out what has to be tested?

Eric Davis wrote:

I don't think the first release of ChiliProject will completely support Ruby 1.9 but I really want to get 2.0 to work with it. Depending on what changes we need to support Ruby 1.9, we might be able to add support to a later minor release of ChiliProject before 2.0 (e.g. 1.2.0, 1.3.0).

AFAIK (and the CI seems to confirm that), 1.9 support is quite good with the latest batch of fixes in Redmine. I think there might still be a couple of minor things not covered by tests, but the basics should be working now already.

Sven Schwyn wrote:

Count me in. Are there any resources to find out what has to be tested?

Well, the tests all seem to pass on 1.9.2 now, so I'd say try it out either locally with a typical workflow, or if you have an install that can bear 1-2 days between "we've found bizarre behavior here" and "there's a fix for that" or for which you can easily switch back and forth between 1.8 and 1.9, try it there.

The best "test" would be to run the system in production under 1.9 and log any exceptions. The test suite is good but it misses a lot of edge cases right now and there are some classes that aren't even tested.

Eric Davis