The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2009-11-01 23h59 UTC.
Removals:
x11-base/x11-drm2009-10-26 16:48:52
battousai
net-wireless/kdebluetooth 2009-10-26 20:28:20
ssuo
01 Nov 2009; Gilles Dartiguelongue package.mask:
Mask app-misc/tracker, bug #291501.
01 Nov 2009; Gilles Dartiguelongue package.use.mask:
Mask tracker USE flag in apps using it, bug #291501.
Tracker-0.7 will soon take over (gnome-2.28 mostly has it already).
--
Gilles Dartiguelongue
Gentoo
On Sun, 1 Nov 2009 17:36:30 +0100
Arfrever Frehtes Taifersar Arahesis wrote:
> Some packages have new releases more than once a month and sometimes it's
> reasonable
> to not skip stabilization of any version. Given version of a package is
> usually no
> longer tested by users after release of
Richard Freeman wrote:
> Mart Raudsepp wrote:
>>
>> Is it stated in any documentation that 30 days is a policy?
>>
>
> Not that I'm aware of - it is a guideline as you indicate. However,
> don't expect anybody to actually take action on a STABLEREQ if there
> isn't some kind of rationale for goin
Mart Raudsepp wrote:
Is it stated in any documentation that 30 days is a policy?
Not that I'm aware of - it is a guideline as you indicate. However,
don't expect anybody to actually take action on a STABLEREQ if there
isn't some kind of rationale for going stable so quickly.
The whole po
# Gilles Dartiguelongue (01 Nov 2009)
# Old gnome component superseeded by seahorse.
# See bug #291456 for details.
gnome-extra/gnome-keyring-manager
--
Gilles Dartiguelongue
Gentoo
signature.asc
Description: Ceci est une partie de message numériquement signée
On Sun, 2009-11-01 at 17:36 +0100, Arfrever Frehtes Taifersar Arahesis
wrote:
> Some packages have new releases more than once a month and sometimes it's
> reasonable
> to not skip stabilization of any version. Given version of a package is
> usually no
> longer tested by users after release of a
Some packages have new releases more than once a month and sometimes it's
reasonable
to not skip stabilization of any version. Given version of a package is usually
no
longer tested by users after release of a newer version, so I suggest the
following
change to the policy of stabilizations:
Stab
