[MAGNOLIA-8298] Adapt Magnolia's versioning schemes (X.Y versions) for permanent SNAPSHOTs Created: 31/Jan/22  Updated: 23/May/22  Resolved: 03/Feb/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.17

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

Attachments: PNG File Screenshot 2022-02-03 at 09.23.00.png    
Issue Links:
Problem/Incident
Relates
relation
is related to BUILD-681 'local-dev' profile to make working w... Open
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

As we uncovered when trying to adopt permanent SNAPSHOTs after 6.2.16's release:

  1. set any Magnolia module with an MVH test class to a permanent SNAPSHOT, e.g. from 6.2.16-SNAPSHOT to 6.2-SNAPSHOT
  2. build it, all the MVH tests fail

We need a PoC that would make this work, and study the implications.

Implementation ideas:

  • X.Y is considered X.Y-99
  • CI-friendly versions


 Comments   
Comment by Roman Kovařík [ 31/Jan/22 ]

I've seen projects using not the X.Y-SNAPSHOT (6.2), but X.Y+1-SNAPSHOT (6.3). Wouldn't that help us?

Comment by Maxime Michel [ 31/Jan/22 ]

rkovarik thanks for the tip but as we already have a 6.3-SNAPSHOT branch in the drawers, this doesn't look a good solution.

Comment by Maxime Michel [ 03/Feb/22 ]

FYI I had to change the Nexus rule that cleans up SNAPSHOTs overnight (see screenshot) so that it no longer removes already released versions, as 6.2-SNAPSHOT artifacts were targeted (6.2 is out).

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