On 09/01/2011 01:58 AM, Hugh Brock wrote:
Hello Aeolus folks.
I've had a number of complaints, or at least expressions of surprise,
recently from Aeolus newcomers about the process we use to post,
review, ACK, and push code to the master repo. Seems we are if not
behind the times at least hidebound, in the eyes of e.g. your typical
github guy.
In general I feel our process has served us well over the last couple
of releases -- in particular, I mandated the
"end-to-end-test-before-ack" policy a while back because we were
getting a high level of "this could never possibly have worked" type
of bugs in the master tree.
However I wonder if we couldn't move faster with some improvements to
the process. Simon Harris sent me
http://scottchacon.com/2011/08/31/github-flow.html this morning as an
example of how things might develop.
Hugh,
I have used topic branches in different projects. Posting patches is
well suited to small projects where details are important, especially
early on in a project's origin. topic branches are well suited to
larger projects where the main concepts and ideas are well understood by
a majority of the developers. We have grown to the point where the
concepts and ideas are well understood making topic branches a good
choice going forward.
Regards
-steve
If any of you have felt restrained by an excess of process in the
project in the past, I'd appreciate you taking the time now to read
the above and propose changes to what we do. Thanks in advance.
Take care,
--Hugh (now returning to vacation)