[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:
Duplicate
duplicates FOLIO-1511 Update dev.folio.org about release br... Closed
Relates
relates to FOLIO-1503 Where should bug fixes be done first? Closed
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:

  • agree on consistent naming conventions
  • updated the docs to talk about how to create and use long-lived release branches and releasing bugfix version off those branches
Comment by David Crossley [ 20/Sep/18 ]

There are some updates to "/guidelines/release-procedures" merged via the related FOLIO-1511 Closed as pull/256, and some more tweaks in pull/257 which also added a section "Release branches and tags" to the "/guidelines/naming-conventions" doc.

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