On Wed, May 25, 2011 at 2:21 AM, Alexandros Frantzis <alexandros.frant...@linaro.org> wrote: > 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.
I've been thinking of using square bracket footnotes to add a bit more detail to things: --- Work items: Design extension foo[1]: TODO Add support for Thumb-2: DONE Add to project bar[2]: POSTPONED [1] will involve the kernel guys. Need to start this early. [2] postponed as it's been merged with blueprint X for next cycle. --- To bikeshed a bit, I prefer sortable dates with the year like 2011-05-25. -- Michael _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
