| 2008-05-29 12:26:13 |
Andrea Corbellini |
bug |
|
|
added bug |
| 2008-05-29 12:31:04 |
Andrea Corbellini |
bug |
|
|
assigned to blueprint |
| 2008-05-29 12:45:31 |
Andrea Corbellini |
description |
Malone and Blueprint allow, respectively, to handle bugs and to draft specifications. Some things which are in Blueprint could be useful for bug reports, like dependency tree and the whiteboard, and other things which are in Malone could be useful for feature specifications, like the ability to send comments and the role of the bug supervisor. Many bugs have been reported to make Blueprint and Malone more similar (like bug #50875, bug #49698, bug #218272, bug #223928), but I think that using the same code (and keeping separate specifications and bugs) would be the best solution. |
Malone and Blueprint allow, respectively, to handle bugs and to draft specifications. Some things which are in Blueprint could be useful for bug reports, like dependency tree and the whiteboard, and other things which are in Malone could be useful for feature specifications, like the ability to send comments, the role of the bug supervisor and the +activity page. Many bugs have been reported to make Blueprint and Malone more similar (like bug #50875, bug #49698, bug #218272, bug #223928), but I think that using the same code (and keeping separate specifications and bugs) would be the best solution. |
|
| 2008-05-29 13:07:55 |
Andrea Corbellini |
description |
Malone and Blueprint allow, respectively, to handle bugs and to draft specifications. Some things which are in Blueprint could be useful for bug reports, like dependency tree and the whiteboard, and other things which are in Malone could be useful for feature specifications, like the ability to send comments, the role of the bug supervisor and the +activity page. Many bugs have been reported to make Blueprint and Malone more similar (like bug #50875, bug #49698, bug #218272, bug #223928), but I think that using the same code (and keeping separate specifications and bugs) would be the best solution. |
Malone and Blueprint allow, respectively, to handle bugs and to draft specifications. Some things which are in Blueprint could be useful for bug reports, like dependency tree and the whiteboard, and other things which are in Malone could be useful for feature specifications, like the ability to send comments, the role of the bug supervisor and the +activity page. Many bugs have been reported to make Blueprint and Malone more similar (like bug #50875, bug #49698, bug #218272, bug #223928), but I think that using the same code, but keeping the two servicies -- specifications and bugs -- separate, would be the best solution. |
|
| 2008-06-04 14:20:04 |
Diogo Matsubara |
blueprint: importance |
Undecided |
Wishlist |
|
| 2008-06-04 14:20:11 |
Diogo Matsubara |
malone: importance |
Undecided |
Wishlist |
|
| 2008-08-22 15:36:02 |
Björn Tillenius |
malone: status |
New |
Invalid |
|
| 2008-08-22 15:36:02 |
Björn Tillenius |
malone: statusexplanation |
|
I'm closing this bug report, since it's too vague. This is better tracked as a blueprint, or better, as individual bug reports. |
|
| 2008-08-22 15:36:12 |
Björn Tillenius |
blueprint: status |
New |
Invalid |
|
