Adopt the gitflow approach to branching: master for releasing stable changes, develop for staging changes, feature branches for features/fixes. Rationale: master is never broken
TimePath
CANCELED
No reason given (by ?)
-
User
Decision
Comment
divVerent
NO
read this as !veto 298 let's rather use gitworkflows which does the same with different branch names (see decision 302).
Halogene
ABSTAIN
I have no idea about git
Nitroxis
NONE
(auto-abstain due to inactivity)
Archer
NONE
(auto-abstain due to inactivity)
bitbomb
NONE
(auto-abstain due to inactivity)
Debugger
NONE
(auto-abstain due to inactivity)
detrate
NONE
(auto-abstain due to inactivity)
FruitieX
NONE
(auto-abstain due to inactivity)
GATTS
NONE
(auto-abstain due to inactivity)
IDWMaster
NONE
(auto-abstain due to inactivity)
JH0nny
NONE
(auto-abstain due to inactivity)
kuniu
ABSTAIN
Mario
YES
Can't hurt to have a more fun version of master available to the daring admins
matthiaskrgr
NO
merlijn
NONE
(auto-abstain due to inactivity)
Mirio
ABSTAIN
Morphed
NONE
(auto-abstain due to inactivity)
nyov
NONE
(auto-abstain due to inactivity)
packer
NONE
(auto-abstain due to inactivity)
s1lence
NONE
(auto-abstain due to inactivity)
sev
NONE
(auto-abstain due to inactivity)
Soelen
NONE
(auto-abstain due to inactivity)
Sydes
NONE
(auto-abstain due to inactivity)
theShadow
NONE
(auto-abstain due to inactivity)
TimePath
YES
Preferably with develop accessible to the entire team so that bad merges can be resolved quickly