Redmine 0.9 release candidate
A release candidate for the new stable branch 0.9 was published today.
You can get it at Rubyforge.
Upgrading from a previous release is pretty straightforward, the few steps to follow are described in RedmineUpgrade.
The release is packaged with Rails 2.3.5.
Comments
Added by Alexey Palazhchenko 8 months ago
Great news!
When do you plan to make a release?
Added by Jean-Philippe Lang 8 months ago
0.9 final is to be released in 10 or 15 days.
Added by Minh-Quân Tran 8 months ago
Do you have any idea why I receive this error:
sudo RAILS_ENV=production rake db:migrate
(in /home/dm/www/ns367178.ovh.net/web/dm/redmine-0.9.0)
rake aborted!
Object is not missing constant Project!
(See full trace by running task with --trace)
Here is all packages installed:
gem list
actionmailer (2.3.5, 2.1.2)
actionpack (2.3.5, 2.1.2)
activerecord (2.3.5, 2.1.2)
activeresource (2.3.5, 2.1.2)
activesupport (2.3.5, 2.1.2)
cgi_multipart_eof_fix (2.5.0)
daemons (1.0.10)
fastthread (1.0.7)
gem_plugin (0.2.3)
mongrel (1.1.5)
mysql (2.8.1)
passenger (2.2.8)
rack (1.1.0, 1.0.1)
rails (2.3.5, 2.1.2)
rake (0.8.7)
rubygems-update (1.3.5)
Added by Balaji Mohandas 8 months ago
Many Thanks for team and the Jeani for their great efforts in making this release. I wish them all a good, successful, happy and prosperous new year.
Added by Otaci Martins 8 months ago
Same error to me:
RAILS_ENV=production rake db:migrate
(in /usr/src/redmine-0.9.0)
rake aborted!
Object is not missing constant Project!
Added by Martin Fischer 8 months ago
Migration of 0.8.4 to 0.9.0 RC works simple and without any problems! Just follow step by step the RedmineUpgrade:[[http://www.redmine.org/wiki/redmine/RedmineUpgrade]]. Great work redmine team!
Added by Minh-Quân Tran 8 months ago
RAILS_ENV=production rake db:migrate
(in /usr/src/redmine-0.9.0)
rake aborted!
Object is not missing constant Project!
-> Try to uninstall rack 1.1.0 and install mysql 2.8.1 if encounter probleme, try mysql 2.7.4
Added by Otaci Martins 8 months ago
Minh-Quân Tran, i'm not using MySQL but PostgreSQL instead and rack 1.1.0 isn't installed.
Look:
actionmailer (2.3.5)
actionpack (2.3.5)
activerecord (2.3.5)
activeresource (2.3.5)
activesupport (2.3.5)
postgres-pr (0.6.1)
rack (1.0.1)
rails (2.3.5)
rake (0.8.7)
Added by Minh-Quân Tran 8 months ago
r u using root or super doer?
Added by Otaci Martins 8 months ago
Both root and sudo
My box:
Fedora 12
kernel 2.6.31.5-127.fc12.i686
ruby-1.8.6.383-4.fc12.i686
Added by Stas SUSHKOV 8 months ago
Hi guys,
I would be happy to upgrade but I can see reasons why not doing that and continue maintaining a personal branch of redmine with community patches.
I thought to the 0.9 release the defect #3780 with OpenID exchange attributes will be solved, but it was not.
Do you plan any fixes for it (not in 0.9 branch, but what about 1.0)?
In current status redmine has support for OpenID, but nobody can use it. Which is very sad.
Cheers and thanks.
Congrats for the upcoming release.
Added by Otaci Martins 7 months ago
Tried with MySQL and it WORKS !
So, perhaps the problem relates to postgresql gem (postgres-pr).
Unfortunatelly we can't go with redmine in production because we prefer PostgreSQL, but at least we can try 0.9.0 in labs until there is a solution.
Specs:
- CentOS 5.3
- ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux]
- rails 2.3.5
- mysql 5.0.77
actionmailer (2.3.5, 2.3.2)
actionpack (2.3.5, 2.3.2)
activerecord (2.3.5, 2.3.2)
activeresource (2.3.5, 2.3.2)
activesupport (2.3.5, 2.3.2)
mysql (2.8.1)
postgres-pr (0.6.1)
rack (1.0.1)
rails (2.3.5, 2.3.2)
rake (0.8.7)
rubygems-update (1.3.5)
Added by Jérémy Lal 7 months ago
postgres-pr is way too old.
See
http://raa.ruby-lang.org/project/postgres-pr/
http://rubyforge.org/projects/ruby-dbi
Also the forum or a new issue could have been a better place
Added by Otaci Martins 7 months ago
SUCCESS !!!
Code:
Gem list:
actionmailer (2.3.5, 2.3.2)
actionpack (2.3.5, 2.3.2)
activerecord (2.3.5, 2.3.2)
activeresource (2.3.5, 2.3.2)
activesupport (2.3.5, 2.3.2)
postgres (0.7.9.2008.01.28)
rack (1.0.1)
rails (2.3.5, 2.3.2)
rake (0.8.7)
rubygems-update (1.3.5)
Added by Joachim Fritschi 7 months ago
The postgres gem itself is outdatet. I had some trouble with the postgres gem recently and updated to the "pg" gem.
http://rubyforge.org/projects/ruby-pg
Added by Andrew Rudenko 7 months ago
Thank you guys to give us this useful product and RC version!
I was successfully updated from 0.8.7 to 0.9RC yesterday. It was gantt-editing patch installed before. And now I have missing the gantt-editing feature. As I know gantt-editing feature was stated for 0.9 release but missing it in the RC.
Will gantt-editing feature be included in the final 0.9 release?
Thanks,
--andrew
Added by Ludovic Gasc 7 months ago
I confirm the success to upgrade Redmine from 0.8.7 to 0.9 RC1 for our instance.
Yours.
Added by David Marín Carreño 7 months ago
I confirm that our upgrade from 0.8.7 to 0.9 RC1, in a Debian 5.0 system, went fine with no problems.
Added by Petrônio Medeiros 7 months ago
When do you plan to make a release?
Added by Thang Nguyen about 1 month ago
Gem list
I've get the same problems so when I've already run those commentactionmailer(2.3.8,2.3.5,2.3.4)
actionpack(2.3.8,2.3.5,2.3.4)
activerecode(2.3.8,2.3.5,2.3.4)
activesupport(2.3.8,2.3.5,2.3.4)
rack(1.1.0, 1.0.1)
rails(2.3.8,2.3.5,2.3.4)
rake(0.8.7)
rubygems-update(1.3.7)
I thought it wasn't installed. So I've moved next to the third command
#gem install postgres raised me errors
ERROR: error installing postgres:
ERROR: Failed to build gem native extensition
/usr/local/bin/ruby extconf.rb
extconf.rb:4:in'<main>' uninitialized constant PLATFORM (NameError)
Gem files will remain installed in /usr/local/lib/ruby/gems/1.9.1/gems/postgres-0.7.9.2008.02.28 for inspection.
Results logged to /usr/local/lib/ruby/gems/1.9.1/gems/postgres-0.7.9.2008.01.28/ext/gem_make.out
I thought It've already installed so I try to run command:
#RAILS_ENV=production rake db:migrate make me upset again with this error :
(in /var/www/html/redmine)
rake aborted!
Object is not misssing constant issue!
(See full trace by running task with --trace)