Hi all, in some of the blueprints I am following, I have noticed that many work items updates (e.g. to DONE/POSTPONED/BLOCKED) are not accompanied by any additional information. Of course, not all work items need more information, but some are meaningless to an external viewer without it.
This is a general observation across Linaro and I am as guilty as any. As an example, consider the following (semi-fictional) work item updates: + Add Qt tracing support for pixmaps: POSTPONED + Create a bazaar branch for libX: DONE + Select and port an application to GLES2: DONE + Test that the application functions correctly on ARM: BLOCKED These updates raise many questions: * Why was Qt tracing for pixmaps postponed? * What is the exact location of the published branch? * Which application was selected for porting? * Where can I find the ported code for the application? * Why is the application test blocked? Such information is usually placed at the top of the whiteboard, like this (at least this is how I am doing it): [alf May 8]: Postponed work on Qt pixmap tracing because it turned out we can trace Qt/Webkit without it, so it is not considered critical anymore. [alf May 10]: Uploaded branch to lp:libX [alf May 10]: Selected application Y for porting to GLES2 [alf May 12]: Finished porting Y to GLES2 and uploaded it to http://git.linaro.org/... [alf May 13]: Blocked on testing the ported application Y because of an issue (LP: #666666) with the 3D drivers for chipset Z. In conclusion, I would like to encourage more verbosity in our updates, so that others can easily follow and appreciate all the great work that we are doing. Thanks, Alexandros _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
