Hi, Did you say that something was missing refers to the second mailing list thread?
First,The Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) threads https://lists.apache.org/thread.html/8201cc5deba2ae846da632a61734873b7bf078335b75726bba02938a@%3Cdev.dolphinscheduler.apache.org%3E Second,The checks about the Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) threads https://lists.apache.org/thread.html/10880d751d0e2a8f2bf9d21bcc72ef21ee1183219ab3514903a01518@%3Cdev.dolphinscheduler.apache.org%3E ________________________________ DolphinScheduler(Incubator) PPMC Gang Li 李岗 [email protected]<mailto:[email protected]> From: Justin Mclean<mailto:[email protected]> Date: 2019-12-04 14:06 To: [email protected]<mailto:[email protected]> Subject: Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available Hi, I still slightly confused, but I'm obviously missing something. > They are doing tests before release check, so the binary tar should be > packaged, source tagged. Then the team could test this tar(s), and make > sure features are ready. Wouldn't they check that while doing the vote? Any connivance binary has to 100% match the source code in the voted on source release. > Then they will use the same tar balls to do PPMC vote, then IPMC. It's highly unusual to vote on a binary release on its own. Apache projects make and release source code not binaries. It's very likely they will need to do another vote on the release, as in it current form the source release is unlikely to pass an IPMC vote. (See my previous email). Thanks, Justin
