| 1 |
On Sun, 11 May 2014 21:49:20 +0300 |
| 2 |
Samuli Suominen <ssuominen@g.o> wrote: |
| 3 |
|
| 4 |
> stable was broken, and now it isn't, everything was done properly, |
| 5 |
> what more motive you need? |
| 6 |
|
| 7 |
QA, none; but Alon needs that motives, hence I asked him to talk to you. |
| 8 |
|
| 9 |
> Then I can't possibly understand your reasoning to intervene on |
| 10 |
> something that doesn't concern you, or the QA team, in the first |
| 11 |
> place, at all Sort of makes this even worse |
| 12 |
|
| 13 |
There's no intervention; as for concern, GLEP 48 says "The QA team is |
| 14 |
also tasked with the authority to ensure tree policies are respected" |
| 15 |
which means that the first logical next step for us is to await your |
| 16 |
talk and check up with the arch teams which is what was did here. |
| 17 |
|
| 18 |
> > I'm expecting apologies from you too, given the statements that I've |
| 19 |
> > quoted in the sub thread, it's a waste of valuable time to everyone |
| 20 |
> > involved, both you and me; so, I do apologize for trying to help |
| 21 |
> > out. |
| 22 |
> |
| 23 |
> Help out? |
| 24 |
|
| 25 |
Yes, help. |
| 26 |
|
| 27 |
> Everything technical (and technical is the only thing that matters to |
| 28 |
> QA) had already been done. |
| 29 |
|
| 30 |
No, that was not the case; the QA team was awaiting technical responses |
| 31 |
from the both of you, as well as the arch teams. |
| 32 |
|
| 33 |
> The time waste is still on-going, with amd64 and x86 unnecessarily on |
| 34 |
> the bug's CC list while they have been already done. |
| 35 |
|
| 36 |
They are aware they are CC-ed and keep themselves CC-ed; so, they are |
| 37 |
free to remove themselves as they see fit. |
| 38 |
|
| 39 |
> So, instead of actually helping out, like filing a new bug for |
| 40 |
> updating the outdated devmanual text regarding major arches |
| 41 |
> stabilizations to reflect statements from their leads, no help was |
| 42 |
> received... |
| 43 |
|
| 44 |
Before we can write up a commit, we first need to know the details; |
| 45 |
I've asked for them in #gentoo-qa, which are still awaiting a response. |
| 46 |
|
| 47 |
> > You know me well enough to know that I'm not messing with your work, |
| 48 |
> > at least not intentionally; if you do see it, feel free to /query |
| 49 |
> > me. |
| 50 |
> > |
| 51 |
> > Please consider to apologize to me in return... |
| 52 |
> > |
| 53 |
> |
| 54 |
> You can expect same tone from me here on out if you continue with |
| 55 |
> intervening on stuff with the QA badge that has no relationship to QA |
| 56 |
> at all, not really going to give an apology for the tone either |
| 57 |
|
| 58 |
We're tasked by GLEP 48 to do so; if that's not expected, feel free to |
| 59 |
propose a change, otherwise the QA team continues to fulfill this task. |
| 60 |
|
| 61 |
-- |
| 62 |
With kind regards, |
| 63 |
|
| 64 |
Tom Wijsman (TomWij) |
| 65 |
Gentoo Developer |
| 66 |
|
| 67 |
E-mail address : TomWij@g.o |
| 68 |
GPG Public Key : 6D34E57D |
| 69 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives