[PUBLISHING-59] Publishing 1.0 branch depends on a maintenance core release Created: 21/Jun/19  Updated: 29/Mar/22  Resolved: 24/Jun/19

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.0.7
Fix Version/s: 1.1

Type: Bug Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PUBLISHING-80 Latest release depends on maintenance... Closed
dependency
duplicate
is duplicated by MAGNOLIA-7577 info.magnolia:magnolia-project depend... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:
Sprint: 6.1 Release Sprint
Story Points: 0.5
Team: Nucleus

 Description   

namely, 5.6.9 (5.6 branch is in maintenance mode since 5.6.8)
5.7.3 and 6.1 depend on the same publishing version, which makes it impossible to build community projects with those versions.

We need a publishing version that doesn't depend on maintenance release, suggesting to bump to 1.1 and depend on 5.7.3 (& boms 5.7.2).

—via SUPPORT-10080


Generated at Mon Feb 12 10:35:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.