🪃
Engineering Playbook
  • Engineering Playbook
  • Agile Development
    • Kanban from the start
    • Daily Stand-up
    • Collaboration
      • Mobile Designer X Mobile Developer
    • Backlog Management
      • Backlog Refinement
    • Card Management
      • Epics
      • User story
        • Collaboration experience with acceptance criteria
        • Proper acceptance criteria
      • Task
      • Bug
      • Hotfix
      • Sub-task
      • Defect
      • Columns
      • Card organization
      • Column Limit
      • Board Templates
    • Pull System Task Assignment
    • Retrospectives
    • Team Agreement
      • Working Agreement
      • Definition of Ready
      • Definition of Done
    • Agile Metrics
  • Github
    • Source Control
    • Merge Strategies
    • Versioning
    • Code Reviews
      • Author's Checklist
      • Reviewer's Checklist
  • Documentation
    • GraphQL as an API Doc
  • DevOps
    • Continuous Integration
Powered by GitBook
On this page

Was this helpful?

  1. Github

Versioning

To achieve loosely coupled components. This will allow developers to detect breaking changes or seamless updates (rollback and new release, A/B Testing, etc) just by looking at the version number

major.minor.patch

  • Major - a breaking change

  • Minor - a backward-compatible minor change

  • Patch - no API change, fixes, or enhancements

PreviousMerge StrategiesNextCode Reviews

Last updated 3 years ago

Was this helpful?