Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vidjil
vidjil
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,688
    • Issues 1,688
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 84
    • Merge Requests 84
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • vidjil
  • vidjilvidjil
  • Merge Requests
  • !884

Open
Opened Jan 13, 2021 by Mathieu Giraud@magiraudOwner0 of 19 tasks completed0/19 tasks
  • Report abuse
Report abuse

Draft: Release 2021.01

  • Overview 1
  • Commits 0
  • Changes 0

Before the release

Documentation

  • New features are described in doc/vidjil-algo.md
  • Breaking changes (and needed configuration changes) are understood

On the feature-a/release branch, the last commit is the release commit updating the three following files:

  • CHANGELOG
  • doc/vidjil-algo.md with the proper release tag
  • algo/release with the proper release tag

Pipelines

https://gitlab.inria.fr/vidjil/vidjil/pipelines/XXXXX (if tests passed on different pipelines, indicate below the relevant pipelines)

Usual tests should pass, but also:

  • prepare_release
  • valgrind_unit
  • valgrind_functional
  • multiple_tests

Benchmarks

  • almost no change...
  • ... or significant changes are understood

The release, publish, tag and push

  • merge this MR to master and tag: git tag release-20XX-XX
  • push: git push origin master release-20XX-XX
  • mirror to GH: git push github master release-20XX.XX
  • click publish_release (there may be changes to CD...)
  • deploy the doc

After these steps, we merge back the release in dev:

  • merge this MR to dev

After the release: deploy

  • Click deploy_release_prod in the deploy_prod stage, deploying the release on vidjil-algo-next on the public server
  • Open a new internal issue with the Deploy (vidjil-algo) template : vdj#XXXXX
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: vidjil/vidjil!884
Source branch: feature-a/release