Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
backbone-message-format backbone-message-format
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Communications Backbone System
  • backbone-message-formatbackbone-message-format
  • Issues
  • #68

Closed
Open
Created Aug 29, 2024 by Dan Jones@danjonOwner31 of 36 tasks completed31/36 tasks

Epic: Release and pin version 1 of the backbone messages

Outcome of discussion on #65 (closed)

  • Release current dev as v1.0.0
  • Create mas-dt branch of message formats from dev
    • #67 (closed) Make schema changes MRs merging into mas-dt branch until below releases are completed
      • #60 (closed) v2.0.0-beta.1 primitives in planning_configuration top-level
      • #73 (closed) v2.0.0-beta.2 semver in message header
      • #47 (closed) v2.0.0-beta.3 geojson in platform_status
      • #61 (closed) v2.0.0-beta.4 geojson in mission_plan actions
      • #77 (closed) v2.0.0-beta.5 squad level primitives
      • #62 (closed) ---- instruction set message
    • Then move to releasing changes as appropriate version bumps
  • Release hydrogen as v1.0.0
  • Release comms backbone as v1.0.0
  • Do the backbone-infrastructure release to pin to v1.0.0 and read from env var
    • Pin schema version to v1.0.0
      • hydrogen
      • argo-adapter (https://git.noc.ac.uk/communications-backbone-system/argo-adapter/-/merge_requests/3)
      • ships-adapter (https://git.noc.ac.uk/communications-backbone-system/ships-adapter/-/merge_requests/4)
      • read from env var
      • default to v1.0.0
      • AND set env var in ansible pinned to v1.0.0 (https://git.noc.ac.uk/communications-backbone-system/backbone-infrastructure/-/merge_requests/20)
    • Pin hydrogen runtime version to v1.0.0
    • Pin comms backbone runtime version to v1.0.0
    • update ansible to serve up swagger for a list of tags
    • create a mas-dt instance of the backbone Going to be done after dry-run mode, but for this epic it's just going on internal-test
  • Do the c2-infrastructure release to pin to v1.0.0 and read from env var
    • backbone-positions-adapter (https://git.noc.ac.uk/oceanids/c2/services/backbone-positions-adapter/-/merge_requests/8)
    • backbone-plan-assistant
    • read from env var
    • default to v1.0.0
    • AND set env var in kustomize pinned to v1.0.0
  • Update adapter repos - add hyphen to regex to accept branch/semver in protocol version
    • backbone-adapter-python
    • backbone-adapter-javascript
  • Update adapter repos to retrieve schema version from nucleus domain instead of gitlab
    • backbone-adapter-python
    • backbone-adapter-javascript
Edited Oct 01, 2024 by James Kirk
Assignee
Assign to
CB-Tech Debt
Milestone
CB-Tech Debt
Assign milestone
Time tracking