You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The module project_status brings statuses or stages on project.project. This has been added in standard (module project) since version 15.0 via project.project.stage.
The module project_status exists in 15.0 and seams to be refused into 16.0, see #1124.
This leads to difficulties form migrating database.
In OpenUpgrade, we can mark the module project_status as merged into project. The right place for doing that is in scripts in 15.0 version.
Doing the migration to standard in 15.0 is as simple as:
But what to do with database in 15.0 that does not use the standard stages but the module project_status ?
Another solution is to mark the module project_status as merged in version 16.0 in OpenUpgrade (which is not correct, but match the state of the this repository). Then the script for migrating data will be a bit more complicated because tables already exists since version 15.0 so we need to copy data from tables to tables and update references.
Or we can do both.
I don't know whats the best approach. Personally, I'm not in the case of using project_status in 15.0, so I'm in favor of the simplest solution: migrating in 15.0.
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
The module
project_status
brings statuses or stages onproject.project
. This has been added in standard (moduleproject
) since version 15.0 via project.project.stage.The module
project_status
exists in 15.0 and seams to be refused into 16.0, see #1124.This leads to difficulties form migrating database.
In OpenUpgrade, we can mark the module
project_status
as merged intoproject
. The right place for doing that is in scripts in 15.0 version.Doing the migration to standard in 15.0 is as simple as:
This script is tested and works.
But what to do with database in 15.0 that does not use the standard stages but the module
project_status
?Another solution is to mark the module
project_status
as merged in version 16.0 in OpenUpgrade (which is not correct, but match the state of the this repository). Then the script for migrating data will be a bit more complicated because tables already exists since version 15.0 so we need to copy data from tables to tables and update references.Or we can do both.
I don't know whats the best approach. Personally, I'm not in the case of using
project_status
in 15.0, so I'm in favor of the simplest solution: migrating in 15.0.@patrickrwilson as maintainer of
project_status
.@pedrobaeza @legalsylvain I ping you because it's related to OpenUpgrade.
The text was updated successfully, but these errors were encountered: