1 On Sat, Jul 18, 2009 at 06:00:46PM -0400, Chris Ball wrote:
2 > > For example, let's assume we have target a, b, c There is a way
3 > > to know that "a" is a past target, "b" is the current target and
4 > > "c" is a future target ?
6 > We could add a "date due" field for each target.
8 Another option would be a "blocked by" field, since you might miss
9 deadlines, or have parallel targeted branches. Or just pick target
10 names following some scheme so the alphanumeric-sort is also a
11 dependency-order sort ;).
13 > > More: there is a way to know if a target is closed or open ?
16 $ be list --target 0.1
17 If there are active bugs, the target is open. Otherwise, you must have
20 > We could add a "target close" operation that moves all open bugs
21 > assigned to one target to the next date-due target.
23 for bug in `be list --target 0.1 --uuids`; do
24 be target $bug $NEXT_TARGET
27 To avoid the loop, we could change status, severity, target, etc from
30 be COMMAND ARG BUG [MORE BUGS ...]
33 This email may be signed or encrypted with GPG (http://www.gnupg.org).
34 The GPG signature (if present) will be attached as 'signature.asc'.
35 For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
37 My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt