Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
O
OHR Support
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 97
    • Issues 97
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Projects
  • OHR Support
  • Wiki
  • Repository use2

Repository use2

Last edited by Javier Serrano Dec 10, 2013
Page history

Policy for repository use in the wrpc-sw, general-cores and wr-cores projects

1. All developers work against a branch called "proposed_master".
2. New features are developed either in a local proposed_master or in a branch and only pushed to ohwr/proposed_master when they are done+tested.
3. The repository maintainer moves proposed_master=>master when it seems in a good state.
4. When a release happens, a branch of master is created by the repository maintainer at that time.
5. The repository maintainer backports critical bug-fixes from proposed_master to the released branch.

Thanks to Wesley Terpstra for proposing the policy on which this one is largely based.

Clone repository
  • Administrator guide
  • Documents
  • Folder structure example
  • Gitlab migration of ohwr faq
  • Home
  • Local git backups
  • News
  • Project structure guidelines
  • Project guidelines
  • Project re structure tips
  • Project review by ht volunteers
  • Repository use
  • Repository use2
  • Documents
    • Ohr logos
    • Ohwr new design visuals
More Pages

New Wiki Page

Tip: You can specify the full path for the new file. We will automatically create any missing directories.