Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Turris Build Turris Build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 97
    • Issues 97
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TurrisTurris
  • Turris OS
  • Turris BuildTurris Build
  • Issues
  • #85
Closed
Open
Issue created Oct 21, 2019 by Karel Koci@kkoci🤘Contributor

Change repository flow

We decided to change repository flow to be more consistent with git flow. The steps to convert current content to new flow is as follows:

  • change documentation (!346 (merged))
  • rename v4.0 to hbk
  • rename v4.1 to hbl
  • rename v5.0 to hbd
  • Mark hbk, hbl and hbd as protected branches
  • set as default branch hbk instead of master
  • drop master branch (preserve as something like future-6.0
  • change HBK build branch to hbk on Jenkins
  • change HBL build branch to hbl on Jenkins
  • change HBD build branch to hbd on Jenkins
  • merge hbk to hbl for initial consistency
  • merge hbl to hbd for initial consistency
  • remove jobs for master on Jenkins
  • Review repository membership (promote to maintainers who has approve himself to understand and accept the workflow)
Edited Apr 09, 2021 by Karel Koci
Assignee
Assign to
Time tracking