Posts Tagged rc
As you might have noticed, we’ve been pushing a lot of Release Candidates out the door. The reason is that we want to make sure 1.0 is really ready for showtime!
This is the final RC before we ship 1.0 final at RubyConf. Here is a really quick rundown of the bugfixes and improvement added to this release:
- Webrat integration out of the box. (see example)
- Improved Merb bundling
- spec view helpers now use nokogiri (with rexml as fallback )
- new have_selector spec helper using CSS3 compatible selector.
- The entire Merb spec suite now runs correctly on JRuby & Windows.
- Once again improved jRuby support.
In other news, we setup a nightly gem server so people who want to be on Edge don’t have to deal with git and we call also test gem releases before pushing to RubyForge. More about that coming up during RubyConf.
Talking about RubyConf,Â Yehuda and I will be in Orlando enjoying a good Ruby meetup. Come and chat with us if you are interested in starting using Merb, or if you have been using Merb. Also, please come and see us if you hate Merb and care tell us why. We’re looking forward to meet you all.
1.0RC1 was released less than a week ago and we are already planning to release RC2 next week or so.
Thanks to all the contributors who reported RC1 bugs and submitted patches. RC2 should iron out most of the small bugs and annoyances encountered.
However, RC2 top priority is to get Merb and DataMapper properly working on Windows. Some members of the .net community offered their help to compile windows native DM drivers. Supporting Windows is not an easy task but we think it is a critical thing to do.
We are also discussing setting up a nightly gem server so people could test Merb edge without having to use git etc..Â It’s also a great way for us to test gem dependencies before an official release. The only problem with nightly gems is that you need to have a way to track what version is being installed or what version a user reporting a bug is using. We do have some ideas, but please feel free to add a comment with your suggestions.
Finally, people on Edge are reporting issue with gems not loading properly. The problem is that you have generated an app with hardcoded dependencies (check your config/dependencies.rb file). Your app won’t load newer gems and therefore migth crash. Make sure to define the proper dependencies. We are working onÂ documenting this behavior and making the error message clearer.