On Mon, Oct 15, 2018 at 7:17 PM Jesse Glick wrote:
> If you have to wonder, the answer is yes. :-)
>
Simple enough!
--
Matt Sicker
Software Engineer, CloudBees
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this
Le mar. 16 oct. 2018 à 02:17, Jesse Glick a écrit :
> On Mon, Oct 15, 2018 at 6:00 PM Matt Sicker wrote:
> > I've thought about a JEP, yes. I'm not sure if the scope warrants it yet.
>
> If you have to wonder, the answer is yes. :-)
>
Heh, I like that.
Proposed
On Mon, Oct 15, 2018 at 6:00 PM Matt Sicker wrote:
> I've thought about a JEP, yes. I'm not sure if the scope warrants it yet.
If you have to wonder, the answer is yes. :-)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe
I've thought about a JEP, yes. I'm not sure if the scope warrants it yet.
I'm currently exploring this as a potential Outreachy mentorship project,
so it might be a bit early still.
On Mon, Oct 15, 2018 at 4:39 PM Liam Newman wrote:
> Matt,
>
> Have you considered make a JEP for this effort?
Matt,
Have you considered make a JEP for this effort? It seems like something
that would benefit from having a design document that captures how the
design was arrived at and what alternatives were considered.
-Liam N.
On Mon, Oct 15, 2018 at 2:28 PM Matt Sicker wrote:
> I've started tasking
I've started tasking out this as an epic:
https://issues.jenkins-ci.org/browse/JENKINS-54082
On Mon, Jul 30, 2018 at 10:38 AM Matt Sicker wrote:
> On Wed, Jul 25, 2018 at 6:03 PM Daniel Beck wrote:
>
>> Doesn't that just mean the listeners need to improved?
>>
>
> Either way, that would
