Reputation
420
Next privilege 500 Rep.
Access review queues
Badges
4 10
Newest
 Yearling
Impact
~7k people reached

  • 0 posts edited
  • 0 helpful flags
  • 13 votes cast
Feb
18
comment In GitHub flow, is it OK to base feature branch on another feature branch?
If only I could wait :)
Feb
18
comment In GitHub flow, is it OK to base feature branch on another feature branch?
Wondering how bad your second set of steps are. Is it a problem in practice that a branch doesn't have a "same" start and end? I don't think it would bother me too much but maybe it's a major mess factor?
Feb
18
comment In GitHub flow, is it OK to base feature branch on another feature branch?
In your third set of steps, the downside is that step 1 needs to contain some "dummy commit". In my situation, I don't have anything useful to commit until required-feature is merged in.
Feb
18
comment In GitHub flow, is it OK to base feature branch on another feature branch?
Many good suggestions, thank you.
Apr
17
comment How to mark next version in the source code?
Maybe the question wasn't clear but it was more about what that @VERSION@ should be, not how to get it to the code technically. I've updated the Q.
Jul
18
comment Feature code + infrastructure code - how to structure the commits / JIRA issues?
Great point. BTW we also typically do multiple commits per one JIRA issue, I just wanted to keep the example simple.
Jul
18
comment Feature code + infrastructure code - how to structure the commits / JIRA issues?
Thanks for such a long reply, however, our issue schemes don't support subtasks. Even if they were, I didn't especially like how JIRA treated hierarchies (they are limited as you pointed out, parent issues cannot display subtask commits etc.). But it's some good information there, thanks.
Jan
2
comment What is the role of traditional issue tracker when Scrum / Kanban board is used?
UX is exactly my problem with JIRA, I was just hoping that GreenHopper fixed that but I will have to find out.
Jan
1
comment What is the role of traditional issue tracker when Scrum / Kanban board is used?
We are a distributed team. Any other suggestions other than JIRA + GreenHopper? What you didn't like about that combo?
Jan
1
comment What is the role of traditional issue tracker when Scrum / Kanban board is used?
Great answer. That may be why I feel JIRA + GreenHopper could be a great solution - it provides both a traditional issue tracker and a virtual board on top of the issues.
Dec
22
comment How does Assembla compare to FogBugz + Kiln
I finally had time to play with Assembla and while I was impressed with the feature list from the description, the UI / UX is so disappointing that I will probably look elsewhere. It's details but for example unreadable paragraphs because of their unlimited width is something I don't want to be dealing with.
Dec
19
comment How does Assembla compare to FogBugz + Kiln
@AntonBarkovsky It's not bad, I'm just looking for an integrated solution where all the services come in one "box".