[FOLIO-2439] contemplate tagging quarterly releases in platform repositories Created: 29/Jan/20  Updated: 03/Jun/20  Resolved: 06/Mar/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Zak Burke Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

It may be helpful to use git tags to label the quarterly releases in platform repositories such as platform-core and platform-complete, but there are some side-effects to consider. On the one hand, it makes it very easy for a person who wants to try out a particular release to find that release. On the other, we currently use branches to identify releases, e.q. q4-2019, q3-2019, etc (i.e. there is already a mechanism in place for trying out particular releases) and those branches may continue to receive patch updates for individual modules after the initial release.

This complicates things:

  • should the tag be moved to the tip of the branch when new patch updates are applied?
  • should the tag stay in place to identify things as they were on the original release?
  • should new tags be added, e.g. flower.1, flower.2 as patch updates are applied?


 Comments   
Comment by Zak Burke [ 06/Mar/20 ]

As the description already notes, adding release-tags to platforms would probably create more problems than it solves. The quarterly release branches do the best job of quantifying what is in a given release.

Generated at Thu Feb 08 23:20:38 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.