Skip to content

Back port decision lost solution for 3.4 which introduced for 3.5/main upgrade #12140

@touhidurabir

Description

@touhidurabir

Description:
Original Issue at #11241
Impacts for 3.4 installation discussed at #11241 (comment)

Solution: What the proposed solutions are and additional affected areas

  1. fixed the migration where this issue introduced for 3.3 to 3.4 upgrade similar to 3.5/main upgrade
  2. introduce a new migration for 3.4.0-x to 3.4.0-y where the solution will be applied for 3.4.0-y upgrade
  3. update 3.5 and main branch migration where the solution has been introduced to have a check if upgrading from 3.4.0-y or above, not to run the fix migration there again

What application are you using?
OJS, OMP or OPS version 3.4.0

Fix Includes

#11876
#12357

PRs

Stable-3.4.0

ojs --> pkp/ojs#5246
omp --> pkp/omp#2275
ops --> pkp/ops#1242

Stable-3.5.0

pkp-lib --> #12457
ojs --> pkp/ojs#5247
omp --> pkp/omp#2274
ops --> pkp/ops#1241

main

Metadata

Metadata

Assignees

Labels

Housekeeping:2:UrgentAny dependency management or refactor that must be done soon to fix or avoid a significant problem.

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions