| 1 |
On ons, 2005-07-13 at 19:49 +0900, Jason Stubbs wrote: |
| 2 |
> If developers aren't open to the idea of adding the information you seek to the ChangeLog, they aren't |
| 3 |
> likely to be open to adding it anywhere. |
| 4 |
|
| 5 |
However, tools can be more or less encouraging. |
| 6 |
|
| 7 |
Regarding the bug# the bug summary can be automaticly pulled in from |
| 8 |
bugzilla. Either, after the fact, when reading the ChangeLog or upon |
| 9 |
submitting it. |
| 10 |
|
| 11 |
I'm not familiar with the QA tools currently used by dev. Would it be |
| 12 |
possible to have theese tools ask the apropritate questions and put them |
| 13 |
into the ChangeLog? |
| 14 |
|
| 15 |
On a related issue, it would be great with a portage-bugzilla tool. |
| 16 |
emerge --info and other stuff could be handled automaticly. When an |
| 17 |
ebuild breaks the tool would be invoked to show filed bugs and their |
| 18 |
links and/or submit a new one. |
| 19 |
|
| 20 |
As it is now portage is great tool for distribution, customization, |
| 21 |
compilation, installation and dependency tracking, it could be a better |
| 22 |
tool with regards to QA and development. |
| 23 |
|
| 24 |
-John |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-portage-dev@g.o mailing list |
Archives