I'm currently pushing hard to get as many outstanding issues wrapped up as possible so we can get a final RC out there and (hopefully) a final release of 1.3.0 shortly thereafter. The plan is to drop a final RC on Monday (9/26) and, barring major problems, a final a few days later.
To expedite this, can anybody who's reported a bug on Lighthouse please double-check to see if it's still applicable to 1.3? I've triaged quite a few, but there's quite a backlog of 1.0-era bugs which may have vanished entirely in the 1.3 rewrites. Oh, and since it's not terribly clear from the documentation, here's how to run a bleeding-edge copy (straight from Git) using Bundler. - Clone the repo someplace handy (I used 'dev', but it's arbitrary). In the cloned repo (dev/hobo) do this: git checkout --track -b rails3 origin/rails3 This will create a tracking branch. To get updates, you can just run 'git pull'. - Add the following to your Gemfile: gem 'hobo_support', :path => 'dev/hobo/hobo_support' gem 'hobo_fields', :path => 'dev/hobo/hobo_fields' gem 'dryml', :path => 'dev/hobo/dryml' gem 'hobo', :path => 'dev/hobo/hobo' Tweak as needed if you didn't put the clone in dev. The notable difference between :path and :git is that the latter only updates the working version if the gemspec's version has changed - and I don't feel that releasing another 20 RCs is a good idea. :) Remove Gemfile.lock and then run 'bundle install'. The net result of all this setup is that you'll be able to grab changes rapidly from Github, so that we can rapidly verify that fixes actually, um... fix. Any questions, feel free to email me or ping me on Gtalk - I'll be working full-time on Hobo all this week and weekend. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
