1.0 was always going to be the last release for Rails 2

There was a lot of development done for Rails 3, but the upgrade
process for Radiant has been painful for a long time. Despite protests
from others, I insisted that we stick to Rails 2 because there were
bugs, missing features, and plenty of painful history of upgrading.
I didn't want to cause problems for developers with existing
installations by jumping to Rails 3 and changing the architecture.
There's a lot more that we can do by making serious changes an a major
number release.

I've already started work for 1.1 to see if we can remove dependencies
from the gemspec and put them into the Gemfile so that you can more
easily opt out of certain features. After that, we'll resurrect the
rails3 branch and start clean.

I'll likely begin pushing Rails 3 changes into the master branch tomorrow.

On Tue, Feb 28, 2012 at 9:24 PM,  <a...@akhlah.com> wrote:
> I thought it would be on Rails 3. Were there problems?
> Al
>> Thank you so much for all your hard work. This is excellent news, and I
>> can't wait to see what happens next.
>> Walter
>> On Feb 28, 2012, at 10:46 AM, Jim Gay wrote:
>>> I'm proud to be able to release 1.0:
>>>    http://radiantcms.org/download/
>>> Many good things have gone into this long-awaited release. The 1.0
>>> series will be the last on Rails 2.
>>> Only minor fixes will go into any further 1.x releases and our effort
>>> will be focused on Rails 3 and further modularization of Radiant.
>>> Radiant is a no-fluff content management system made for designers and
>>> programmers and is ideal for use on small teams. It is similar to
>>> Movable Type or Textpattern, but is much more than a blogging engine.
>>> Radiant features:
>>>   * An elegant user interface
>>>   * The ability to arrange pages in a hierarchy
>>>   * Flexible templating with layouts, snippets, page parts, and a
>>>     custom tagging language (Radius: http://radius.rubyforge.org)
>>>   * A dynamic extension system
>>>   * A simple user management/permissions system
>>>   * Support for Markdown and Textile as well as traditional HTML
>>>     (it's easy to create other filters)
>>>   * Operates in two modes: dev and production depending on the URL
>>>   * A caching system which expires pages every 5 minutes
>>>   * Built using Ruby on Rails (which means that extending Radiant is
>>>     as easy as any other Rails application)
>>>   * Licensed under the MIT-License
>>>   * And much more...
>>> There's even a live demo over on the project Web site:
>>>    http://radiantcms.org/demo/
>>> Radiant now runs on Ruby 1.9!
>>> We now support Bundler and have a default way to manage attachments,
>>> stylesheets (with support for Sass/SCSS), JS (with support for
>>> CoffeeScript),
>>> built-in page preview, and many more features.
>>> https://gist.github.com/1540782
>>> Radiant wouldn't be possible without the help of some fine people. The
>>> following people have made contributions to this release:
>>> Jason Taylor                    Johannes Fahrenkrug
>>> William Ross                    Mark Reginald James
>>> John Muhl                        Samuel Whited
>>> Benny Degezelle              Josh French
>>> Jim Gay                          Oriol Gual
>>> Wes Gamble                    Michal Cichra
>>> Michael Stalker                Andrew vonderLuft
>>> Chris Parrish                    Dirk Kelly
>>> Jeff Casimir                     vanderhoorn
>>> John Long                        Mario Visic
>>> Gert Goet
>>> https://github.com/radiant/radiant/contributors
>>> The best place to get support is definitely on the Radiant mailing list.
>>> There's a crowd of people there who have been hanging around for many
>>> moons now. Newbie questions are welcome! To sign up, go to:
>>> http://radiantcms.org/mailing-list/
>>> The Radiant mailing list is also accessible via Ruby forum:
>>> http://www.ruby-forum.com/forum/21
>>> Enjoy!
>>> --
>>> Jim Gay
>>> for the Radiant CMS Dev Team
>>> http://radiantcms.org

Write intention revealing code #=> http://www.clean-ruby.com

Jim Gay
Saturn Flyer LLC

Reply via email to