Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
6
Impact
~1k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Jul
16
awarded  Popular Question
Jul
2
comment Git branch model critique: always derive from master
@Ewan You say git is kind about that, are there any side-effects nonetheless?
Jul
2
comment Git branch model critique: always derive from master
My main concern in this question is if there is something I'm overseeing and if there's something that might be worse in this model in this scenario. Your concerns about runtime bugs and how to fix them is exactly the kind of feedback I'm here for, thanks =]
Jul
2
comment Git branch model critique: always derive from master
About shortening the release cycle, we already do many releases a week. Many features are small and fast, but some features are slow and deal with jelly outside services. What I'm trying to do with this model is protect the small fast features from getting infected by the slow and jelly ones.
Jul
2
comment Git branch model critique: always derive from master
When runtime integration bugs arise, the affected feature-set team will be assigned to correct it. If it is caused by code from features created by any of the other teams, fixes are made into pull requests to the offending feature branch. Pull requests are then reviewed by the team that owns that feature, merged in and then merged into the release package. The team that knows how a feature should work makes the fix, the team who owns the offending code reviews it.
Jul
2
comment Git branch model critique: always derive from master
@gbjbaanb master is not QA. Only code that is already in production goes to master, and only after a release cycle that does not result in a rollback, so code is guaranteed to be safe for other developers to branch from. That's the whole point: prevent branching or merging from a failed release package.
Jul
2
asked Git branch model critique: always derive from master
Feb
27
awarded  Supporter
May
18
revised Making an internship most effective, useful and fun for both parties
added 5 characters in body
May
18
awarded  Teacher
May
18
revised Making an internship most effective, useful and fun for both parties
added 348 characters in body
May
18
awarded  Editor
May
18
revised Making an internship most effective, useful and fun for both parties
added 348 characters in body
May
18
answered Making an internship most effective, useful and fun for both parties
May
16
awarded  Scholar
May
16
accepted Peter Norvig's paper cited by Brendan Eich
May
16
awarded  Student
May
16
asked Peter Norvig's paper cited by Brendan Eich