1 |
On 11/14/2013 12:21 AM, James wrote: |
2 |
> hasufell <hasufell <at> gentoo.org> writes: |
3 |
> |
4 |
> |
5 |
>> Our arch testers are understaffed and often don't really do general |
6 |
>> runtime tests (it's mostly assumed the maintainer knows about runtime |
7 |
>> issues). |
8 |
> |
9 |
>> I have often had a hard time to get some random users comment on |
10 |
>> certain packages or even assist on some runtime tests. I don't even |
11 |
>> know how many people use the package I maintain. |
12 |
> |
13 |
> |
14 |
> When a new package is installed or upgraded, there are notes that the |
15 |
> installer is optioned (and notified upon installation) about the |
16 |
> package. Might it be a good idea to put your testing pleadings |
17 |
> in the notes for those how install the package (stable, testing, |
18 |
> experimental or overlay) about how to contact whoever related to |
19 |
> the specific testing you want done? I. E. "eselect news" or is this |
20 |
> a bad idea? |
21 |
> |
22 |
> |
23 |
> JFFNMS is one of my favorite packages, so surely I'd respond on that |
24 |
> one. Hell, I often go and find the patches and post bugs pleading to |
25 |
> get documented patches installed on my favorite package. |
26 |
> |
27 |
> |
28 |
> hth, |
29 |
> James |
30 |
> |
31 |
> |
32 |
|
33 |
I think people will not like having that in eselect news. There could be |
34 |
a similar thing like: |
35 |
|
36 |
eslect test-requests |
37 |
|
38 |
but the question is if that will get bloated and other stuff I'm not |
39 |
sure about. |
40 |
|
41 |
The easiest thing I can think of is a project site on our wiki which |
42 |
would also point to relevant bugs. Then again... who really wants to |
43 |
maintain that. |
44 |
|
45 |
All other ideas are even more advanced. |
46 |
|
47 |
I wonder if we could add a keyword on bugzie like REQUSERTEST... so |
48 |
bored users could easily get a list of such bugs. But who would really |
49 |
use that? |