Upgrade to Ruby 1.9
Reported by Marnen Laibow-Koser | September 9th, 2011 @ 04:59 PM
We shouldn't stay on Ruby 1.8 forever, particularly now that we're using Rails 3.
Comments and changes to this ticket
-
Marnen Laibow-Koser September 9th, 2011 @ 06:39 PM
- State changed from “new” to “open”
Working on this.
-
Marnen Laibow-Koser September 9th, 2011 @ 07:15 PM
- State changed from “open” to “resolved”
- Tag changed from “ruby1.9, upgrade” to “ruby1.9, upgrade, v0.3.1”
Wow, that was incredibly painless. Merging into master for v0.3.1.
-
-
Marnen Laibow-Koser September 9th, 2011 @ 07:16 PM
(from [7216c796aa6d357c4cfbc5cf85fc254a7cffad27]) Add Rake task to put in encoding headers. [#58] https://github.com/marnen/quorum2/commit/7216c796aa6d357c4cfbc5cf85...
-
Marnen Laibow-Koser September 9th, 2011 @ 07:16 PM
(from [86a87493d68c00a7b7f8d95c91b5ff90a29d9f53]) Incredibly, RSpec needs Test::Unit. [#58] https://github.com/marnen/quorum2/commit/86a87493d68c00a7b7f8d95c91...
-
Marnen Laibow-Koser September 9th, 2011 @ 07:16 PM
(from [b9790deb939a525719a88b9088589e50950c0920]) Add UTF-8 encoding headers. [#58] https://github.com/marnen/quorum2/commit/b9790deb939a525719a88b9088...
-
Marnen Laibow-Koser September 9th, 2011 @ 07:16 PM
(from [4cbc3037991ef3ac4fd4e48ae4612a77ae100c19]) Fix a couple of syntax issues that Ruby 1.9 doesn't like. [#58] https://github.com/marnen/quorum2/commit/4cbc3037991ef3ac4fd4e48ae4...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
<p>This is the issue tracker for the Quorum calendar system. Also see our <a href="http://github.com/marnen/quorum2">Github repository</a> and our <a href="http://quorum2.sourceforge.net">project website</a>.</p>
<p>Please tag bug reports with <strong>bug</strong> and feature requests with <strong>feature</strong>. Use additional descriptive tags as necessary.</p>
Marnen Laibow-Koser