On Tue, May 24, 2011 at 04:04:11PM +0100, Peter Maydell wrote:
On 24 May 2011 15:21, Alexandros Frantzis alexandros.frantzis@linaro.org wrote:
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.
Perhaps we could improve the tools to encourage this/make it easier?
For instance, the work item format could be improved to let you add accompanying commentary to items rather than insisting on a strict one-line-only approach. As you say, you can add stuff at the top of the whiteboard, but that gets a bit messy and hard to cross-reference.
If work items were officially supported as a launchpad/blueprint feature then you could design the UI to encourage the addition of a little commentary when a work item is ticked off.
Proper support for named and timestamped comments (like bug reports have) might also help.
It really feels like it could be time to promote the work items to a real entity in launchpad. Has this been discussed before?
Many of the things we seem to want (ability to attach metadata, a proper audit trail, ability to mine) are natural database features, so it seems unfortunate that this all has to be achieved with scripts and obscurely formatted text buried inside text fields in launchpad.
But this situation has existed for a long time, so maybe it's not so simple as that... ?
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.
As a bodge, you can add extra text to the work item itself when changing its state, though this will quickly get unwieldy.
---Dave