* Re: [gentoo-dev] rfc: revisiting our stabilization policy
@ 2014-01-16 22:49 99% ` Tom Wijsman
0 siblings, 0 replies; 1+ results
From: Tom Wijsman @ 2014-01-16 22:49 UTC (permalink / raw
To: pinkbyte; +Cc: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Thu, 16 Jan 2014 10:20:37 +0400
Sergey Popov <pinkbyte@gentoo.org> wrote:
> It can not go to no result, unless we have no breakages in stable,
> stable REMAINS stable. If it contains old, but working software - then
> it is stable.
An ebuild promoted to stable is because an arch team (or a privileged
maintainer to do it individually) has put a keyword in place. The
person that puts that keyword in place, defines that the ebuild is
stable at that specific point in time.
However; this does not imply that as the ebuild gets older, that this
doesn't come without problems; neither does it imply that the software
is totally working. Software is rarely completely without bugs.
> As i said earlier, problem begins when we NEED to stabilize something
> to prevent breakages and arch teams are slow.
Yes; there is a big correlation between breakages in old versions and
stabilization, in both ways.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-01-14 21:37 [gentoo-dev] rfc: revisiting our stabilization policy William Hubbs
2014-01-14 23:49 ` Tom Wijsman
2014-01-15 11:40 ` Sergey Popov
2014-01-15 17:04 ` Tom Wijsman
2014-01-16 6:20 ` Sergey Popov
2014-01-16 22:49 99% ` Tom Wijsman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox