...

• Branch creation and pull-request to update the ACS release version
• Integration branch creation (integration/COMMON-YYYYMMM)
• Confluence page for the release notes
• Jenkins (or build system in use) jobs for ACS

A template for the ticket could be as follow:

Subject: Create COMMON-2019JUN YYYYMMM core tasks

Description:

This ticket is to track the creation of repeatable tasks to be done for COMMON-2019JUNYYYYMMM release:
* Branch + Pull request for change of tag version of ACS (.bash_profile.acs and ACS_VERSION files)
* Create confluence page with release notes and other general information for the release
* Create Jenkins tasks to generate ExtProds, build, test and release new versions

...

• Using JIRA-Bitbucket functionality, create the branch associated with the ticket
• Go to your repository and checkout the branch you just created
• Edit the following two files by changing the release version to the new one
  • ACS/ACS_VERSION
  • ACS/LGPL/acsBUILD/config/.acs/.bash_profile.acs
    
    • In this file look for the definition of 'ALMASW_RELEASE' environment variable
• Make your commit including the ticket number in the description
• Push your changes to BitBucketto Bitbucket

Integration Branch

Do the following actions:

• Using Bitbucket functionality, create a branch called 'integration/COMMON-YYYYMMM' using the master as starting point

Confluence

Do the following actions:

...

git status
...


git log --no-merges --oneline master..integration/COMMON-2019JUNYYYYMMM -- ACS
...


git log --no-merges --oneline master..integration/COMMON-2019JUNYYYYMMM -- ARCHIVE
...


git log --no-merges --oneline master..integration/COMMON-2019JUNYYYYMMM -- ICD
...

• Confirm the system requirements are still valid and update accordingly

...

Jenkins – From scratch

 TODO

Finishing

After finishing the tasks summarized in here, we have our first implemented ticket. At this point we're ready to follow with all the other Implementation.