Re: Last call for review of Test-Builder using Test2 (Formerly Test-Stream)

--001a11403fd4590f70052b1b63d7
Content-Type: text/plain; charset=UTF-8

I am certainly not going to consider 24 hours of silence a reason to stamp
a stable label on it. Rjbs and I have a status meeting every week, if
things were completely silent for 2 weeks we were going to evaluate the
situation and move on from there.

In addition we still need people from the qa hackathon in berlin to confirm
or reject the assertion that their punch list items are satisfied before
the Test::Builder component can be marked stable. If they choose to be
silent on this thread we will reach out to them directly.

My point is, things are not going to happen over night, and silence will
not be taken as a seal of approval. That said, indefinite silence will also
not be considered a blocker past a point, but no time limits have been set
either way.

-Chad
On Feb 6, 2016 2:13 AM, "Kent Fredric" <[email protected]> wrote:

> On 6 February 2016 at 08:14, Chad Granum <[email protected]> wrote:
> > If there is anything in these
> > distributions (Test2 in particular) that makes you uncomfortable, you
> > need to speak now.
>
>
> Mentioning here for visibility:
>
> As with Test-Stream where the apparent silence lead to a premature
> conclusion that finalisation was appropriate, I feel interpreting the
> current lull in activity in the same way equally premature.
>
> I've seen a proposal floating around that might raise our ability to
> be confident about the feature set of Test2 before requiring its
> implementation/feature-freeze.
>
> Just the people who I talked to who implied they were going to present
> said proposal haven't yet had the tuits to do so yet.
>
>
> --
> Kent
>
> KENTNL - https://metacpan.org/author/KENTNL
>

--001a11403fd4590f70052b1b63d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I am certainly not going to consider 24 hours of silence a r=
eason to stamp a stable label on it. Rjbs and I have a status meeting every=
 week, if things were completely silent for 2 weeks we were going to evalua=
te the situation and move on from there.</p>
<p dir=3D"ltr">In addition we still need people from the qa hackathon in be=
rlin to confirm or reject the assertion that their punch list items are sat=
isfied before the Test::Builder component can be marked stable. If they cho=
ose to be silent on this thread we will reach out to them directly.</p>
<p dir=3D"ltr">My point is, things are not going to happen over night, and =
silence will not be taken as a seal of approval. That said, indefinite sile=
nce will also not be considered a blocker past a point, but no time limits =
have been set either way.</p>
<p dir=3D"ltr">-Chad</p>
<div class=3D"gmail_quote">On Feb 6, 2016 2:13 AM, &quot;Kent Fredric&quot;=
 &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt;=
 wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 6 Februar=
y 2016 at 08:14, Chad Granum &lt;<a href=3D"mailto:[email protected]">exod=
[email protected]</a>&gt; wrote:<br>
&gt; If there is anything in these<br>
&gt; distributions (Test2 in particular) that makes you uncomfortable, you<=
br>
&gt; need to speak now.<br>
<br>
<br>
Mentioning here for visibility:<br>
<br>
As with Test-Stream where the apparent silence lead to a premature<br>
conclusion that finalisation was appropriate, I feel interpreting the<br>
current lull in activity in the same way equally premature.<br>
<br>
I&#39;ve seen a proposal floating around that might raise our ability to<br=
>
be confident about the feature set of Test2 before requiring its<br>
implementation/feature-freeze.<br>
<br>
Just the people who I talked to who implied they were going to present<br>
said proposal haven&#39;t yet had the tuits to do so yet.<br>
<br>
<br>
--<br>
Kent<br>
<br>
KENTNL - <a href=3D"https://metacpan.org/author/KENTNL" rel=3D"noreferrer" =
target=3D"_blank">https://metacpan.org/author/KENTNL</a><br>
</blockquote></div>

--001a11403fd4590f70052b1b63d7--