[FOLIO-1717] Document release procedure for feature/major and patch Created: 17/Jan/19 Updated: 05/May/21 Resolved: 05/May/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Adam Dickmeiss | Assignee: | Adam Dickmeiss |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| Description |
|
The steps currently does not tell exactly how to make a long-lived release branch and how to release from it. Update the documentation on that. |
| Comments |
| Comment by Adam Dickmeiss [ 18/Jan/19 ] |
|
David Crossley : https://github.com/folio-org/folio-org.github.io/pull/321 |
| Comment by Jakub Skoczen [ 18/Jan/19 ] |
|
Adam Dickmeiss The PR looks good to me. I would also like to add a general overview of the branching model used in FOLIO, something like: FOLIO Branching Model In FOLIO, generally, we use three types of branches:
|
| Comment by David Crossley [ 21/Jan/19 ] |
|
I have merged Adam's PR. Regarding Jakub's suggestion: I wonder if that should be added to the "Git and branches" section of the "Guidelines for Contributing Code" and link to it from the release procedures. |
| Comment by Adam Dickmeiss [ 21/Jan/19 ] |
|
See
|