[MAGNOLIA-8447] Release process exception: merge boms into main Created: 01/Jun/22  Updated: 27/Oct/22

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Release automation
Team: Foundation

 Description   

As suggested by mgeljic. boms sharing the BUILD Jira project with other deliverables, it's release process deviates from the standard, which is that each module has a Jira project where its versions are defined directly. In the case of boms, the versions look like 'BOMs 6.2.20' rather than '6.2.20' only. That being said, the impact on the release process is low.


Generated at Mon Feb 12 04:32:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.