[FOLIO-1482] update dev.folio.org with information on release branches Created: 11/Sep/18 Updated: 17/Jan/19 Resolved: 17/Jan/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint46 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Description |
|
Need information on what is the purpose of master (next dev release) and maintaining release branches (for the purpose of release bugfixes). From there derive appropriate maven/npm configuration. Adam Dickmeiss Marc Johnson Jakub Skoczen |
| Comments |
| Comment by Jakub Skoczen [ 17/Sep/18 ] |
|
The procedures here https://dev.folio.org/guidelines/release-procedures/ are inconsistent and don't mention long-lived (bugfix) release branches which we need starting from Q3. Can we please:
|
| Comment by David Crossley [ 20/Sep/18 ] |
|
There are some updates to "/guidelines/release-procedures" merged via the related
|