diff options
Diffstat (limited to '.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments')
16 files changed, 0 insertions, 336 deletions
diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4012c6cc-1300-4f6b-af0e-9176eedf8de7/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4012c6cc-1300-4f6b-af0e-9176eedf8de7/body deleted file mode 100644 index 552b2ea..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4012c6cc-1300-4f6b-af0e-9176eedf8de7/body +++ /dev/null @@ -1,56 +0,0 @@ -On Mon, Jul 20, 2009 at 05:03:18PM -0400, Chris Ball wrote: -> Hi Gianluca, -> -> > 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 -> -> Okay, sounds reasonable. Would you like to write a patch for -> associating due dates and open/closed with a target? - -I've been mulling this over, and I think that targets are a lot like -bugs. Here's a list of issue/implementation pairs: - - * Targeting normal bugs - - With "be depend". I think we should remove the "target" field from - bugs, and move target dependencies over into the "be depend" - framework. Of course, we could add "blocks" (in addition to the - current "blocked-by") tags to make target lookup more efficient. - - * "due_by" - - We could add "due-by" to Bug.extra_strings as well, so that anyone - could set due dates for any issue they wanted. - - * Bugdir-wide target - - Just a pointer to the current target bug. - - * Target dependency tree / time-series. - - Use BLOCKS/BLOCKED-BY tags between targets, so you'd know which ones - came first. - - * be target list - - Would become "be list --severity target". A target "severity" would - keep target bugs distinct from other bug/issue types. - - * Commenting on targets - - They'd be Bug()s, so commenting already build in, e.g. to add - release notes, layout roadmaps, etc. - -If you want, we could maintain the current "be target" interface, -and just use all this stuff behind the scenes. - -Thoughts? -Trevor - --- -This email may be signed or encrypted with GPG (http://www.gnupg.org). -The GPG signature (if present) will be attached as 'signature.asc'. -For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy - -My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4012c6cc-1300-4f6b-af0e-9176eedf8de7/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4012c6cc-1300-4f6b-af0e-9176eedf8de7/values deleted file mode 100644 index c93321b..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4012c6cc-1300-4f6b-af0e-9176eedf8de7/values +++ /dev/null @@ -1,11 +0,0 @@ -Alt-id: <20090801102742.GA29000@mjolnir.home.net> - - -Author: W. Trevor King <wking@drexel.edu> - - -Content-type: text/plain - - -Date: Sat, 1 Aug 2009 06:27:42 -0400 - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body deleted file mode 100644 index c799630..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body +++ /dev/null @@ -1,47 +0,0 @@ -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 diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values deleted file mode 100644 index 5b9011f..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values +++ /dev/null @@ -1,14 +0,0 @@ -Alt-id: <200907202259.11774.gian@grys.it> - - -Author: Gianluca Montecchi <gian@grys.it> - - -Content-type: text/plain - - -Date: Mon, 20 Jul 2009 22:59:11 +0200 - - -In-reply-to: 6555a651-5a7f-4a8a-9793-47ad1315e9e8 - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/64424f05-b42b-4835-8afd-8495ae61345d/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/64424f05-b42b-4835-8afd-8495ae61345d/body deleted file mode 100644 index 08595d1..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/64424f05-b42b-4835-8afd-8495ae61345d/body +++ /dev/null @@ -1,8 +0,0 @@ -Implemented. - -You can now list targets by dependency (not by date, but better for -most cases) with - be depend -t-1 --severity target ID -where ID is the uuid of any target bug, or with - be depend -t-1 --severity target $(be target --resolve TARGET) -where TARGET is the summary of any target bug. diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/64424f05-b42b-4835-8afd-8495ae61345d/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/64424f05-b42b-4835-8afd-8495ae61345d/values deleted file mode 100644 index 3925aa2..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/64424f05-b42b-4835-8afd-8495ae61345d/values +++ /dev/null @@ -1,11 +0,0 @@ -Author: W. Trevor King <wking@drexel.edu> - - -Content-type: text/plain - - -Date: Sun, 06 Dec 2009 05:42:52 +0000 - - -In-reply-to: 4012c6cc-1300-4f6b-af0e-9176eedf8de7 - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/body deleted file mode 100644 index ef09dc0..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/body +++ /dev/null @@ -1,26 +0,0 @@ -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. - - > 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. - -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. - -- Chris. --- -Chris Ball <cjb@laptop.org> - -_______________________________________________ -Be-devel mailing list -Be-devel@bugseverywhere.org -http://void.printf.net/cgi-bin/mailman/listinfo/be-devel diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/values deleted file mode 100644 index 5de3e0c..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/values +++ /dev/null @@ -1,14 +0,0 @@ -Alt-id: <m3skgt648h.fsf@pullcord.laptop.org> - - -Author: Chris Ball <cjb@laptop.org> - - -Content-type: text/plain - - -Date: Sat, 18 Jul 2009 18:00:46 -0400 - - -In-reply-to: b9865d8b-46ae-4169-bc83-d75a98164729 - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/7750d77c-85d2-4810-9d41-cec62b0da885/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/7750d77c-85d2-4810-9d41-cec62b0da885/body deleted file mode 100644 index 874d906..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/7750d77c-85d2-4810-9d41-cec62b0da885/body +++ /dev/null @@ -1,20 +0,0 @@ -On Monday 20 July 2009 23:03:18 Chris Ball wrote: -> Hi Gianluca, -> -> > 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 -> -> Okay, sounds reasonable. Would you like to write a patch for -> associating due dates and open/closed with a target? - -Ok. As soon as I finish a basic implementation of the html export, I will be -glad to try to write a patch. - -bye -Gianluca - -_______________________________________________ -Be-devel mailing list -Be-devel@bugseverywhere.org -http://void.printf.net/cgi-bin/mailman/listinfo/be-devel diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/7750d77c-85d2-4810-9d41-cec62b0da885/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/7750d77c-85d2-4810-9d41-cec62b0da885/values deleted file mode 100644 index 0d96f8e..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/7750d77c-85d2-4810-9d41-cec62b0da885/values +++ /dev/null @@ -1,14 +0,0 @@ -Alt-id: <200907202340.39963.gian@grys.it> - - -Author: Gianluca Montecchi <gian@grys.it> - - -Content-type: text/plain - - -Date: Mon, 20 Jul 2009 23:40:39 +0200 - - -In-reply-to: 777182da-a216-45c7-bf4d-42c84e511c66 - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/777182da-a216-45c7-bf4d-42c84e511c66/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/777182da-a216-45c7-bf4d-42c84e511c66/body deleted file mode 100644 index 13505c1..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/777182da-a216-45c7-bf4d-42c84e511c66/body +++ /dev/null @@ -1,19 +0,0 @@ -Hi Gianluca, - - > 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 - -Okay, sounds reasonable. Would you like to write a patch for -associating due dates and open/closed with a target? - -Thanks, - -- Chris. --- -Chris Ball <cjb@laptop.org> - -_______________________________________________ -Be-devel mailing list -Be-devel@bugseverywhere.org -http://void.printf.net/cgi-bin/mailman/listinfo/be-devel diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/777182da-a216-45c7-bf4d-42c84e511c66/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/777182da-a216-45c7-bf4d-42c84e511c66/values deleted file mode 100644 index bf069fc..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/777182da-a216-45c7-bf4d-42c84e511c66/values +++ /dev/null @@ -1,14 +0,0 @@ -Alt-id: <m3hbx72hk9.fsf@pullcord.laptop.org> - - -Author: Chris Ball <cjb@laptop.org> - - -Content-type: text/plain - - -Date: Mon, 20 Jul 2009 17:03:18 -0400 - - -In-reply-to: 4952e1c7-e035-42f1-882b-6b5264481d0a - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/9bbe9370-99c7-4d7c-80ee-9ade6b6feb9f/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/9bbe9370-99c7-4d7c-80ee-9ade6b6feb9f/body deleted file mode 100644 index a916904..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/9bbe9370-99c7-4d7c-80ee-9ade6b6feb9f/body +++ /dev/null @@ -1,37 +0,0 @@ -On Sat, Jul 18, 2009 at 06:00:46PM -0400, Chris Ball wrote: -> > 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. - -Another option would be a "blocked by" field, since you might miss -deadlines, or have parallel targeted branches. Or just pick target -names following some scheme so the alphanumeric-sort is also a -dependency-order sort ;). - -> > More: there is a way to know if a target is closed or open ? - -There's also - $ be list --target 0.1 -If there are active bugs, the target is open. Otherwise, you must have -made it ;). - -> We could add a "target close" operation that moves all open bugs -> assigned to one target to the next date-due target. - -for bug in `be list --target 0.1 --uuids`; do - be target $bug $NEXT_TARGET -done - -To avoid the loop, we could change status, severity, target, etc from - be COMMAND BUG ARG -to - be COMMAND ARG BUG [MORE BUGS ...] - --- -This email may be signed or encrypted with GPG (http://www.gnupg.org). -The GPG signature (if present) will be attached as 'signature.asc'. -For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy - -My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/9bbe9370-99c7-4d7c-80ee-9ade6b6feb9f/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/9bbe9370-99c7-4d7c-80ee-9ade6b6feb9f/values deleted file mode 100644 index 0f4ff0a..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/9bbe9370-99c7-4d7c-80ee-9ade6b6feb9f/values +++ /dev/null @@ -1,14 +0,0 @@ -Alt-id: <20090718222701.GA304@mjolnir.home.net> - - -Author: W. Trevor King <wking@drexel.edu> - - -Content-type: text/plain - - -Date: Sat, 18 Jul 2009 18:27:01 -0400 - - -In-reply-to: 6555a651-5a7f-4a8a-9793-47ad1315e9e8 - diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/b9865d8b-46ae-4169-bc83-d75a98164729/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/b9865d8b-46ae-4169-bc83-d75a98164729/body deleted file mode 100644 index 7382bae..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/b9865d8b-46ae-4169-bc83-d75a98164729/body +++ /dev/null @@ -1,20 +0,0 @@ -Hello - -Just a question and only for curiosity: there is an easy way to determine the -target succession ? - -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 ? More: there is a way to know if a target is -closed or open ? - -thanks - -bye -Gianluca - - -_______________________________________________ -Be-devel mailing list -Be-devel@bugseverywhere.org -http://void.printf.net/cgi-bin/mailman/listinfo/be-devel diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/b9865d8b-46ae-4169-bc83-d75a98164729/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/b9865d8b-46ae-4169-bc83-d75a98164729/values deleted file mode 100644 index 6f56640..0000000 --- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/b9865d8b-46ae-4169-bc83-d75a98164729/values +++ /dev/null @@ -1,11 +0,0 @@ -Alt-id: <200907182351.03217.gian@grys.it> - - -Author: Gianluca Montecchi <gian@grys.it> - - -Content-type: text/plain - - -Date: Sat, 18 Jul 2009 23:51:03 +0200 - |