incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)
Date Thu, 16 Feb 2017 00:48:31 GMT

On 2/15/17, 4:37 PM, "John D. Ament" <> wrote:

>So here's my point of view.  Justin's provided some more context on how to
>shape licenses.  If you feel very strongly that the release should go out
>the door, the way it is, then I am OK with changing my vote to a +1.  If
>however, you're like me, and would prefer accuracy over speed, I think its
>worth your time to fix the remaining license issues, package up a CR10,
>see that the IPMC votes +1 without reservations (it gives better
>that you can cut an ASF release).
>I'm even willing to help you rewrite your license file for accuracy.

Here's another possible way to think about it:  A podling really should be
trying to graduate ASAP.  My project only cut one release before
graduating.  If you are pretty certain you are going to cut another
release before graduating, I would ship RC9 and fix it for the next
release.  And even if you aren't going to cut another release before
graduating, since the point of incubation is education, unless anybody in
the IPMC thinks you haven't learned enough, I'd say you have.

That's because to me, an even more important aspect than choosing
"accuracy over speed" is whether your community and RM has the time and
energy to go through another RC after 9 RCs so far.  Sometimes it is
better to ship and take a break from the RC train, especially if you are
sure you are going to cut another release while in incubation.  The
foundation probably isn't at risk here.  Community over code.

My 2 cents

View raw message