foser wrote:
Hi,
as others wrote there are some policies on how to mark stable and that it shouldn't normally happen the day after something has been added to ~.
On the other hand it is just a fact that a lot of ~arch upgrading happens trough stumbling over it (so a lot of packages stay longer than needed in ~arch), there have been some efforts to attack this problem, but not too successful. This is an issue that needs attention and ideas on how to solve this in a satisfactory manner. Since you seem to actively care about getting things to stable (not everybody does), maybe you have some ideas on how this should be handled ?
How about gentoo-stats? Im not familiar with the project but maybe it could be used to correlate
users using package x marked ~arch to to the number of bug reports on x and packages that depend on x ?
Personally, I keep all my make.conf's ACCEPT_KEYWORDS commented out, and maintain my overlay in subversion with my own ideas of stable ebuilds.
When I have been using a package in my overlay successfully for some time, I could do a genlop -t package-name file a bug report then leave it to the devs, but the Im not sure how well that works as I have yet to see many|any of my reports cause a change in the portage tree.
Bugzilla is just not the perfect place for bump-to-stable requests & stability feedback on ~.
- foser
-- [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
