Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

  1. SVS Bitbucket repo
  2. JIRA Project
  3. Release and tagging 
  4. Web upgrade
  5. Journey upgrade 

 

Info
titleSVS Bitbucket Repository Management

SVS Bitbucket Repo

  • We
keep out
  • manage SVS DSL source code
on the
  • in Bitbucket with Git
  • Master - Tags - Here resides the currently deployed production code
      1. Tags - Labeled in the with the following versioning standard numeric value X.Y.X , e.g 1.0.0
        1. X.Y.X refers to <MAJOR>.<MINOR>.<PATCH>
        2. Increment in X should happen only when there is to a Major release , such newly release SVS 2.0.0 Module containing the Stock Receiving Functionality
        3. Y - Recent improvements in the current Module. This should contain release from client request and Team Major Maintenance request.
        4. X - Small patches release such as bug fixes on a production.
        5. Team must still decide if it wants prefix be for the versioning. e.g svs-1.0.0 or svs-musika-1.0.0
      2. Developer - Should be branched from master and used as a current branch where all developer branches are created and merged to while waiting deployment deployment to production. 

...

Info
titleJIRA Project Management

JIRA Project

  • All current development work must be documented through JIRA tickets .
  • All tickets must reflect their target project code
  • Development work that involves a commenting to the Bitbucket must be committed / created / reflected on the Ticket
  • Each Major release version must be have been reflected in a form on an epic on JIRA

JIRA 

 

Filter by label (Content by label)
showLabelsfalse
max5
spacesES
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "sourcecontrol" and type = "page" and space = "ES"
labelsSourceControl

...