Poky Contrib: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(Create exemption list, document pruning process)
 
(→‎Exempt poky-contrib Branches: add a branch QA are using as part of their regular testing)
 
Line 7: Line 7:
These branches need to stay in place but are no longer receiving updates. They might be referenced in documentation or used in established workflows. Please feel free to add your branches.
These branches need to stay in place but are no longer receiving updates. They might be referenced in documentation or used in established workflows. Please feel free to add your branches.


* cagurida/compliance
* rpurdie/daisy
* rpurdie/daisy
* rpurdie/datasock
* rpurdie/datasock

Latest revision as of 14:59, 26 September 2017

Poky Contrib Pruning

To keep poky-contrib from growing endlessly we move branches that have not been updated to poky-contrib-archive. We are planning to do this quarterly.

Before doing the move we will e-mail users so they can prune branches that do not need to be archived.

Exempt poky-contrib Branches

These branches need to stay in place but are no longer receiving updates. They might be referenced in documentation or used in established workflows. Please feel free to add your branches.

  • cagurida/compliance
  • rpurdie/daisy
  • rpurdie/datasock
  • rpurdie/jethro
  • rpurdie/krog
  • rpurdie/master-next
  • rpurdie/mpx
  • rpurdie/multiconfig
  • rpurdie/mut
  • rpurdie/mut-rp
  • rpurdie/nfsroot
  • rpurdie/python3
  • rpurdie/pythonsdkfixes
  • rpurdie/rewitt
  • rpurdie/tizen
  • rpurdie/wip
  • rpurdie/wip-rss
  • rpurdie/wip-rss2
  • rpurdie/wip-temp
  • rpurdie/wip-temp2
  • rpurdie/wip5
  • rpurdie/wipqueue
  • rpurdie/wipqueue2
  • rpurdie/wipqueue3
  • rpurdie/wipqueue4