launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #02113
Re: Build engineer report, Dec 2009
Jonathan Lange wrote:
However, I also conducted a bit of a survey on what the pain points of
Launchpad development are. There were only five respondents, but even
then, there was a strong message: the TDD cycle is too slow, and the
cycle of making branches & landing them is too slow. News at 11. Full
survey results at http://paste.ubuntu.com/345051/
Jono, thanks for running the survey. It is great to get some concrete information on what people are thinking, even if it's not news :)
So our branch-and-fix cycle is too slow. I was wondering, which steps are still present when people work on other projects with faster development cycles? Bazaar? Django? Twisted? Zope? And when you work on that other project, are the steps faster or slower to run?
Also, when I fixed the bug in the AppServer layer, I kept a detailed
record of everything I did and how long it took. If someone (perhaps
the next build engineer? perhaps you?) were interested, they could
make a small value-stream map from the timeline, or write some tools
to automate the more repetitive steps.
Steps: http://paste.ubuntu.com/345058/
Timeline: http://paste.ubuntu.com/345057/
I must often run 'rocketfuel-get', 'link-external-sourcecode', 'make', and 'make schema' to create a branch, and that means five to ten more minutes of waiting to start work on the actual problem. (Unfortunately I can not time those steps right now: perhaps someone else could?)
I am not sure that there is enough information in http://paste.ubuntu.com/345057/ to draw a value stream map. Perhaps it would help if we knew which steps feel like you are doing something, and which steps feel like you are waiting? Waiting is waste, too.
Maris
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References