bzr-pipeline patches for 0.2 release
zygmunt.krynicki at linaro.org
Sat Oct 2 22:03:59 UTC 2010
I was trying to improve my work flow and I finally used bzr-pipeline for
change management. I have prepared a rather big pipeline with 13
different patches that collectively add some of 0.2 features, some minor
enhancements, bug fixes etc.
I did not know what to expect of pipeline plug-in so the patches I
produces directly reflect my old development style (hack until glad with
result) rather than some carefully planned design.
I'd like to ask you for advice on how to propose all of this for
merging. I used bzr sync-pipeline to publish all of the pipeline
components on launchpad (as lp:~zkrynicki/launch-control/stable.pipe).
Should I just mark each one as ready for review? I could also export the
whole pipeline as a series of patches (I like that but it's somewhat
against our nice review system on lp.net). I have no experience with
this yet, so if anyone knows of a better way feel free to point me out
PS: IMHO pipeline is a really good tool and I hope we can continue using it.
More information about the linaro-dev