Identify and Select SHA1

SHA1s for each repo are identified by PTLs. If the project is integrated with other projects (such as installer projects) it is important to communicate with these projects as well.

In order to identify and select the SHA1 to use for tagging, use either the Gerrit web interface, or the git commands, as listed below.

https://gerrit.opnfv.org/gerrit/gitweb?p=<YOUR PROJECT NAME>.git;a=shortlog;h=refs/heads/stable/Hunter

-- OR --

git checkout stable/Hunter
if that doesn't work ("error: pathspec 'origin/stable/Hunter' did not match any file(s) known to git"):
git checkout origin/stable/Hunter
git log --graph

Tagging (complete SHA1 process above first)

Tagging goes through gerrit review as any normal patchset, and the actual tagging will be automated upon submit. Exactly as was done for Hunter branching.

  1. In a similar fashion to 'branches:' add a 'releases:' section to $yourproject.yaml in the releng repository. 
    1. Please add Trevor Bramwell and Aric Gardner as reviewers when you create this patchset.
  2. Once you have the SHA1 that you want to release for the Hunter branch, clone the releng repository
  3. Edit: releng/releases/Hunter/"$yourproject".yaml

Here is an example of a project.yaml file documenting releases 8.0.0, 8.0.1 and 8.1.0. Note: $SHA1 and $project below is the actual project name and git reference, and not meant to be literal. Documentation on the project.yaml file and it's fields can be found in the Release Engineering docs.

# SPDX-License-Identifier: Apache-2.0
##############################################################################
# Copyright (c) 2018 The Linux Foundation and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Apache License, Version 2.0
# which accompanies this distribution, and is available at
# http://www.apache.org/licenses/LICENSE-2.0
##############################################################################
---
project: $yourproject
project-type: installer
release-model: stable

releases:
  - version: opnfv-8.0.0   <- Only 
    location:              <- For
      $yourproject: $SHA1  <- 8.0.0 release
  - version: opnfv-8.0.1   <- Only 
    location:              <- For
      $yourproject: $SHA1  <- Bug Fixes
  - version: opnfv-8.1.0   <- Don't add this section until the 8.1.0 release 
    location:
      $yourproject: $SHA1

branches:
  - name: stable/Hunter
    location:
      $yourproject: $SHA1 <-this is the ref where master and Hunter originally diverged. Once set it never changes. 

release-notes: http://docs.opnfv.org/en/stable-Hunter/submodules/$yourproject/docs/release/release-notes/release-notes.html


For each release you only need to add one version and one ref: examples below.

releases:
  - version: opnfv-8.0.0
    location:
      $yourproject: $SHA1
 
if you have a last minute, minor change, then simply repeat the process and increment the third digit, e.g.,

releases:
  - version: opnfv-8.0.1
    location:
      $yourproject: $SHA1


  - version: opnfv-8.1.0
    location:
      $yourproject: $SHA1

if you have a last minute, minor change, then simply repeat the process and increment the third digit, e.g.,

  - version: opnfv-8.1.1
    location:
      $yourproject: $SHA1


  - version: opnfv-8.2.0
    location:
      $yourproject: $SHA1

if you have a last minute, minor change, then simply repeat the process and increment the third digit, e.g.,

  - version: opnfv-8.2.1
    location:
      $yourproject: $SHA1

Troubleshooting