Skip to content

Instantly share code, notes, and snippets.

@ancorgs

ancorgs/branches.md

Last active November 21, 2016 10:00
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ancorgs/e518824c191097d0be580e7e727389a9 to your computer and use it in GitHub Desktop.
Save ancorgs/e518824c191097d0be580e7e727389a9 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
branches.md

What should go to SP2 branch?

As I understand, only stuff relevant for SP2 itself (good reason for it to be in a future MU)

What should go to CASP branch?

Everything that goes to SP2 + CASP specific stuff

Versions

  • master -> 3.2.A
  • SP2 ---> 3.1.B
  • CASP --> 3.1.C.D

Bad examples

So?

Changes introduced in SP2 should be merged to CASP and master

The storage-ng

Please, if you introduce changes in master of a repo that contains a storage-ng branch, merge the changes there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment