Team Votes(#298)

Back
ID Category Title Creator Status Result
298legacyAdopt the gitflow approach to branching: master for releasing stable changes, develop for staging changes, feature branches for features/fixes. Rationale: master is never brokenTimePathCANCELED2:2(3 abstained, 20 didn't vote)
-
User Decision Comment
divVerentNOread this as !veto 298 let's rather use gitworkflows which does the same with different branch names (see decision 302).
HalogeneABSTAINI have no idea about git
NitroxisNONE(auto-abstain due to inactivity)
ArcherNONE(auto-abstain due to inactivity)
bitbombNONE(auto-abstain due to inactivity)
DebuggerNONE(auto-abstain due to inactivity)
detrateNONE(auto-abstain due to inactivity)
FruitieXNONE(auto-abstain due to inactivity)
GATTSNONE(auto-abstain due to inactivity)
IDWMasterNONE(auto-abstain due to inactivity)
JH0nnyNONE(auto-abstain due to inactivity)
kuniuABSTAIN
MarioYESCan't hurt to have a more fun version of master available to the daring admins
matthiaskrgrNO
merlijnNONE(auto-abstain due to inactivity)
MirioABSTAIN
MorphedNONE(auto-abstain due to inactivity)
nyovNONE(auto-abstain due to inactivity)
packerNONE(auto-abstain due to inactivity)
s1lenceNONE(auto-abstain due to inactivity)
sevNONE(auto-abstain due to inactivity)
SoelenNONE(auto-abstain due to inactivity)
SydesNONE(auto-abstain due to inactivity)
theShadowNONE(auto-abstain due to inactivity)
TimePathYESPreferably with develop accessible to the entire team so that bad merges can be resolved quickly
unfaNONE(auto-abstain due to inactivity)
zykureNONE(auto-abstain due to inactivity)