On Sun, Mar 8, 2020 at 4:52 PM Justin Mclean <justinmcl...@me.com.invalid> wrote: > > Hi, > > > Yes, this is the key point why I am asking this question: we need > > stable the mainline and make the first apache release. > > Apache doesn’t actually care if your release works or not [*], it not an ASF > requirement that a build must pass all tests. What matters is that the next > build is better than the last one. We would prefer that project make frequent > releases, gradually improving things, and not put off a release trying to > make it perfect. One path leads to community growth, the other to community > decline, I’ll let you guess which is which.
But how we measure the release become better and better? 1.All config/host build without error 2.The testsuit has the growing pass rate Both are the reasonable indicator that the project is on the right direction, is it right? > > Thanks, > Justin > > [*] The project and it’s user might care more about this :-)
