Permalink
Browse files

HTML changes force major version change, might as well go 1.0

  • Loading branch information...
1 parent c318a2c commit c6f73b18872de3e6a85bd4b2d2d8b8e201b7a40d @parndt parndt committed Dec 30, 2010
Showing with 5 additions and 5 deletions.
  1. +1 −1 lib/news.rb
  2. +2 −2 readme.md
  3. +2 −2 refinerycms-news.gemspec
View
@@ -2,7 +2,7 @@ module Refinery
module News
class << self
def version
- %q{0.9.9.6}
+ %q{1.0}
end
end
end
View
@@ -19,14 +19,14 @@ Key features:
Include the latest [gem](http://rubygems.org/gems/refinerycms-news) into your Refinery CMS application's Gemfile:
- gem "refinerycms-news", '~> 0.9.9'
+ gem "refinerycms-news", '~> 1.0'
Then type the following at command line inside your Refinery CMS application's root directory:
bundle install
rails generate refinerycms_news
rake db:migrate
-
+
## Customising the views
Type this command at your project root to override the default front end views:
View
@@ -1,8 +1,8 @@
Gem::Specification.new do |s|
s.name = %q{refinerycms-news}
- s.version = %q{0.9.9.6}
+ s.version = %q{1.0}
s.description = %q{A really straightforward open source Ruby on Rails news engine designed for integration with RefineryCMS.}
- s.date = %q{2010-11-11}
+ s.date = %q{2010-12-31}
s.summary = %q{Ruby on Rails news engine for RefineryCMS.}
s.email = %q{info@refinerycms.com}
s.homepage = %q{http://refinerycms.com}

0 comments on commit c6f73b1

Please sign in to comment.