Reputation
302
Top tag
Next privilege 500 Rep.
Access review queues
Badges
3 11
Newest
 Editor
Impact
~6k people reached

Apr
10
answered Testing code in Java that is only loosely defined
Apr
9
answered Having a production branch or using master?
Mar
13
awarded  Editor
Mar
13
revised Understanding basics of object declaration in Java
Spelling changes
Mar
13
suggested approved edit on Understanding basics of object declaration in Java
Mar
1
answered Bad sign if nobody can comprehend one's code?
Dec
4
awarded  Yearling
Nov
21
awarded  Nice Question
Sep
24
awarded  Autobiographer
Sep
12
awarded  Citizen Patrol
Aug
24
awarded  Notable Question
Sep
17
awarded  Popular Question
Feb
27
awarded  Scholar
Feb
27
accepted Is a merging strategy like Git Flow really an anti-pattern?
Feb
25
awarded  Caucus
Feb
25
awarded  Constituent
Feb
20
comment Is a merging strategy like Git Flow really an anti-pattern?
Doing a bit of reading up on it, and Martin Fowler's reference seems to indicate that feature branches done in a continuous integration flow can work out - if they're done in smaller bites than what most people would consider doing them for. So, in a sense, you're right - less than two weeks as a time-to-live on a feature branch seems suitable. I don't see, however, how feature branches themselves are the anti-pattern.
Feb
19
comment Is a merging strategy like Git Flow really an anti-pattern?
@ErikReppen: I'd like to take everyone's minds away from version control and have a process that everyone can get used to. This way, we don't have to worry about things like if this is an anti-pattern or not.
Feb
19
comment Is a merging strategy like Git Flow really an anti-pattern?
Nah, not using branches is a non-starter. The other primary issue would be that work can be done in two different places in the same code, so hopefully we can do something to alleviate that, too.
Feb
19
comment Is a merging strategy like Git Flow really an anti-pattern?
My experience with feature branches, or the way we've done them, is that there can be heartache with them if they're allowed to live for more than an iteration. A rule that states that all features must be merged into the iteration before release would be nice, to alleviate the heartache of merges - and boy, have we had some serious heartache behind those...