Hi

I am trying to migrate an old 3.8.0 chiliproject database on an ubuntu machine 14.04 (operating on virtualbox). My fault for waiting so long. I’ve followed the various migration guides - it is a nightmare :-) not a single gemfile works from the beginning (at least for v2.4;3.0;3.017;4.0;4.1;4.2). I suspect that the gems evolved so much during 3 years that new dependencies appear.

Maybe when writing
gem 'foo','>=0.17' one should write gem 'foo','=0.17' ?

Because after 3 years the gem is likely to be in v3.5 with broken compatibility. Somehow there should be an option in bundle to use the minimum specified version of all gems?

Before writing a full report on the issues I ran into, I would like to know whether I can directly switch to OPv6.0 and use the “common” migrating command:

bundle install npm install RAILS_ENV="production" bundle exec rake db:migrate RAILS_ENV="production" bundle exec rake db:seed RAILS_ENV="production" bundle exec rake assets:precompile

or shall I follow each particular version, and in fact which ones because it is advised to use the last stable ones, ie 3.0.17 instead of 3.0, 4.0.12 instead of 4.0. Do I have to go through 2.4.03.0.17>4.0.124.1.4>4.2.95.0.19>6.0 ?

It takes a lot of time to make all these versions work (migration and server). Especially that “work” is difficult to define, eg in 2.4.0 the “menu” “Home>main project>sub project” did not work but is working in “3.0” therefore it is difficult to discriminate between database and openproject issues. My current strategy is to focus on migration and check by the end. I am currently in 4.0 (migration succeed, but the server fails with sass issues).

Thanks.

PS: my base is very simple, we only used it as a bug tracker, no news, no wiki, no gantt, no plugins… I had the hope it could have been simple.