with upgrade, you might have to declare ownership again for the www folder.
I had no luck doing the SVN option. Here is what I did
I had alot of issues trying to follow just one walkthrough so I pieced together alot of them and found things that worked. I am in no way an expert on this nor am I even a novice.... I just have vshpere where I snapshot and then trial and error. Finally got it to work and I believe below is the only commands I used.
This is all done with a baseline turnkey redmine with 2.2.3. I had some plugins i wanted to try which required an upgrade... so here it is...
If you made any changes to the locales/en.yml then you will have to do it again. I wouldn't recommend copying that file over as the update might have some other language associations that werent with the older version.
SNAPSHOT VM FIRST!!!**
cd /var/www/
mv redmine redmine-old
wget http://www.redmine.org/releases/redmine-2.5.2.zip
unzip redmine-2.5.2.zip -d /var/www/
mv redmine-2.5.2 redmine
cp redmine-old/config/database.yml redmine/config/database.yml
cp redmine-old/config/configuration.yml redmine/config/configuration.yml
cp -r redmine-old/files redmine/
cp -r redmine-old/plugins redmine/
bundle install --without development test rmagick
bundle exec rake generate_secret_token
bundle exec rake db:migrate RAILS_ENV=production
bundle exec rake redmine:plugins:migrate RAILS_ENV=production
cd redmine
chown -R root:www-data /var/www/redmine
chown -R www-data:www-data files/ log/ tmp/ public/plugin_assets
reboot
log into your webserver as admin=>administration=>information
and you should see that it was upgraded. Ensure that there is no error with the plugin write access. You may have to go in and change ownership of some stuff. This is where it got funky with mine and I forgot what I did so I think the above commands is what I did but not sure.