Re: [gentoo-dev] Arches marking ebuilds stable before maintainer

[Donnie Berkholz]

Carsten Lohrke said:
> As Donnie said: package.mask'ed ebuilds most likely result either in
> less bug  reports or more users whining about broken stuff, because a
> lot of them would  unmask nearly everything then. When becoming a dev I
> was told, that an ebuild  can/should be marked stable thirty days after
> the last known bug is fixed.  Does every arch team member adhere this
> rule and look at bugs.g., if there is  an open bug report left and if
> the last ebuild change is from a month ago,  before declaring an ebuild
> stable on xyz?

Part of the problem is the difficulty of knowing you've found all bugs
related to a given package. Since we have no bugzilla category for each
package, this relies on each bug having a useful and relevant summary
containing the package name. That simply isn't the case right now.

Donnie



--
gentoo-dev@g.o mailing list