I installed plugin openproject-costs with branch => “stable/6”.

But when I start the server after running ‘bundle install’, a error indicates:

openproject_costs plugin requires OpenProject version = 6.1.0 but current version is 6.2.0. (Redmine::PluginRequirementError)

How could I resolve this problem? apart from rolling back openproject version to 6.1 or waiting for next version of openproject-costs.

Hi Xia,

I believe you’re using the dev branch of the core which is versioned for the next major release (6.2.0). You need to check out matching branches or tags when using the plugin manually.
That is, either continue running on a development version of OpenProject by using dev as well on the costs plugin, or check out stable/6 on both.
The former should work most of the time, but there may be significant changes and bugs since that’s our integration branch.

FYI: OpenProject packaged installation includes the Costs plugin.

Best,
Oliver

Thanks, Oliver! It works with dev branch.

I did an install of release 6.1 on macOS 10.12.2 and followed the instructions for manual installation.

I stumbled at the point RAILS_ENV=“production” ./bin/rake db:migrate with the error

Redmine::PluginRequirementError: openproject_costs plugin requires OpenProject version = 6.1.4 but current version is 6.1.5.

What shall I do?

Thanks
Frank

If I use the dev branch (i.e. without —branch option), it’s okay.

If I use the dev branch (i.e. without —branch option), it’s okay.

Hi Frank,

just a quick info about the versions we provide, and the ones we suggest you to use:

Branches

• dev branch, our development branch throughout the core and all plugins, this is next major or minor release. (Currently, this is targeting OpenProject 6.2.0)

• release/6.1 is the development branch for the immediate next patch release, it will mostly be stable, but it reflects the next unreleased version (currently 6.1.5, which is what I guess you checked the core out). That means, this branch contains versions 6.1.0 - 6.1.x.

• stable/6 is the stable branch we build our packages from. Use this branch for manual installation if you can’t use the packaged version.

If you install a plugin managed by us, you’ll find the same branches on these plugins, and you should always check out the matching branch(es). In our packaged installation, all plugins are vendored into the package so the versioning is done implicitly.

Best,
Oliver