| 1 |
On 01/04/2017 08:09 AM, Michael Palimaka wrote: |
| 2 |
> On 04/01/17 12:57, Andrew Savchenko wrote: |
| 3 |
>> Hi all, |
| 4 |
>> |
| 5 |
>> On Sun, 25 Dec 2016 22:55:27 +0300 Andrew Savchenko wrote: |
| 6 |
>> [...] |
| 7 |
>>> Another question: do we steel need to set STABLEREQ keyword for |
| 8 |
>>> stabilization bugs? Since we now have a dedicated Stabilization |
| 9 |
>>> component, STABLEREQ looks redundant. |
| 10 |
>> |
| 11 |
>> Ping here. |
| 12 |
>> |
| 13 |
>> Best regards, |
| 14 |
>> Andrew Savchenko |
| 15 |
>> |
| 16 |
> |
| 17 |
> With the changes, STABLEREQ and KEYWORDREQ indeed become redundant. |
| 18 |
> |
| 19 |
> That said, it's entirely possible some arch team members are relying on |
| 20 |
> these keywords for old saved searches etc. With so many people working |
| 21 |
> in isolation, it's difficult to know who is doing what. |
| 22 |
> |
| 23 |
|
| 24 |
Not sure if I like this, isn't it anyways still required for security |
| 25 |
vulnerabilities bumping etc, so now we have a branching of processes |
| 26 |
depending on project/category selections that needs to be taken into |
| 27 |
consideration? |
| 28 |
|
| 29 |
-- |
| 30 |
Kristian Fiskerstrand |
| 31 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 32 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives