blob: c799630c681fe5993cb53bee125f4dffaf831262 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
On Sunday 19 July 2009 00:00:46 Chris Ball wrote:
> Hi,
>
> > For example, let's assume we have target a, b, c There is a way
> > to know that "a" is a past target, "b" is the current target and
> > "c" is a future target ?
>
> We could add a "date due" field for each target.
Good idea
> > More: there is a way to know if a target is closed or open ?
>
> We could add a "target close" operation that moves all open bugs
> assigned to one target to the next date-due target.
Nice. But instead of moving all bugs to the next date-due target, I'd prefer
to leave the choice to the user
> I see problems with these ideas in general, because we're assuming
> agreement by all parties/branches on when a target's date due is.
> Maybe it's okay to demand that social conventions be used to handle
> such a disagreement, or maybe not.
I don't see these as problems per se. We can have two cases:
1) a personal branch (like my html output or Trevor's email interface). In
this case there is not any problem to decide the due date
2) a branch with a group of delopers (let it be the canonical branch o an
experimental branch): in this case I suppose that working together means to be
able to agree on some things
In any case, having the possibility to set a due date does not means that it
is obligatory to do it and should be a good idea to offer as many possibilities
as we can to the users of BE
bye
Gianluca
_______________________________________________
Be-devel mailing list
Be-devel@bugseverywhere.org
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
|
