1 |
[Okay, I have not read the entire thread as I came in on it late] |
2 |
|
3 |
I think the problem is not primarily the fault of the Gentoo developers. |
4 |
I see it as more as a issue with the "~" group: the brave souls who run |
5 |
gentooware in the testing branch. My understanding is that Gentoo |
6 |
developers put stuff in ~* and expect to hear back from testers via |
7 |
bugs.gentoo.org. Whether or not we have problems they expect to hear |
8 |
from us, even if it's to say "ebuild x-y-z builds and runs fine on x86." |
9 |
Most of us "~" users (myself included) simply upgrade new software and |
10 |
if it doesn't work we go on our merry old way. I'm guilty of this too. |
11 |
But I think this gives the Gentoo developers the impression that it's |
12 |
not been tested enough because not a lot of people are providing |
13 |
feedback. We usually only speak up when something is *not* working. We |
14 |
need to be more assertive if we are going to be "~" testers, because the |
15 |
Gentoo developers look to us to determine if/when should go in the |
16 |
stable branch. |
17 |
|
18 |
So the next time you install a piece of software in the testing branch, |
19 |
go to bugs.gentoo.org and see if their is an open item on that release. |
20 |
If not open one yourself, but whatever you do, let the developers and |
21 |
other users know your experiences running the new release on your |
22 |
respective platforms. |
23 |
|
24 |
Gentoo developers: please correct me if I'm wrong. |
25 |
|
26 |
-m |
27 |
|
28 |
|
29 |
-- |
30 |
gentoo-dev@g.o mailing list |