|
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?
|