Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • SA3LI Trial SA3LI Trial
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SA3
  • SA3LI TrialSA3LI Trial
  • Issues
  • #2
Closed
Open
Issue created Mar 17, 2020 by carignani@carignaniOwner

Tagging convention

Context

The trail currently has a convention of:

  • Tagging the merge commit that merges the relevant "meeting" branch (i.e. the output of plenary)
  • Labelling the tag as "vX.Y.Z"
  • Release notes for the tag contains a link to the specification on the 3GPP portal
  • Release notes for the tag also contain the rows from Annex Z (Change History) that changed since the previous version.

Questions

  1. Is this a good convention?
  2. Would also be nice to indicate whether each of the CRs actually changes the ASN.1 or XSD?
  3. Should we also include a CHANGELOG as would be common in many other open source projects? Or is this too much of a maintenance burden?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking