Workflow & tools

[Gustavo Niemeyer]

Hey there,

We were just talking here in the sprint about how to improve our
current workflow.. there are a few problems we'd like to solve, so
I'll write down some ideas about things we have to manage every day
and things we should be able to do better so that we can reach an
agreement about the right tool to use.

Here are a few different aspects that must be tracked as far as change
life-cycle goes.   Note that multiple reviews per branch are the norm.

- Which branches am I pushing
- Which branches must I review now (assigned to me, specifically)
- Which branches can I review now (pending team-level reviews)
- Which of my branches have been reviewed, and are pending fixes from me
- Which of my branches have been reviewed, and are mergeable
- Which of the branches I reviewed are pending follow ups from me
- Team-level overviews for all of the above
- Which bugs are scheduled for the current milestone and to whom
(possibly no one)

Our current workflow to achieve these includes bugs, branches, merge
proposals, manual changes to the global status of the merge proposal
(which is often forgotten), and one bug per branch (which is often
out-of-date, and heavy to use).

The solution we come up with should cover not only feasibility, but
should also be extremely simple to insert, review, and update, making
it pleasant to use and more likely for the tasks to be up-to-date.

There are a few different ideas floating around for how to solve them,
and this is an attempt to write down the basic requirements.

-- 
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog

-- I never filed a patent.