[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: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| 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:
We need a PoC that would make this work, and study the implications. Implementation ideas:
|
| 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). |