[FOLIO-1718] extending guidelines on versioning Created: 18/Jan/19  Updated: 08/Feb/21

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

Type: Task Priority: P2
Reporter: Jakub Skoczen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-1746 SPIKE: When should a major behavioura... Closed
is blocked by FOLIO-1748 include edge-rtac in folio-snapshot/t... Closed
Relates
relates to FOLIO-1767 Ensure that ModuleDescriptor and RAML... Open
relates to FOLIO-1746 SPIKE: When should a major behavioura... Closed
relates to FOLIO-1736 SPIKE: When used by clients, JSON sch... Closed
Sprint: CP: ready for planning
Story Points: 3
Development Team: Core: Platform

 Description   

The current guideline here needs to be extended with more information https://dev.folio.org/guidelines/contributing/#version-numbers.

  • adding mandatory vs optional fields
  • changing behavior
  • adding permissions
  • documentation change in the schema/RAML

Kostyantyn Khodarev Marc Johnson



 Comments   
Comment by Jakub Skoczen [ 16/Sep/19 ]

David Crossley Marc Johnson Guys, do we need more guidelines still or is the latest published guidelines enough?

Comment by Marc Johnson [ 16/Sep/19 ]

Jakub Skoczen

do we need more guidelines still or is the latest published guidelines enough?

Personally, I think we need better guidelines, with examples of what to do in common scenarios and when to make the changes e.g. for a breaking interface change, update the interface version and the implementation version in the pull request

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