You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by qiao zhanwei <qi...@outlook.com> on 2019/11/26 07:23:48 UTC

[ANNOUNCE] Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Hello everyone,

The test build of 1.2.0 is available, This is our first Apache release.

Compared to round 2, we fix one bug

We welcome any comments you may have, and will take all feedback into account if a quality vote is called for this build.

Release notes:

   - https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0/ReleaseNotes.md (fix one bug)

Release Candidate:

- https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/1.2.0
   - sha512 checksums
      - 3fc00e4f0f1705101cf999cb35cfba04c927d1988fd2e7a679443acbfbf4e032b926681c44570fb2d0c6d5f2f6122ac6419e56d5adda6d9199ccccff3917fef0  apache-dolphinscheduler-incubating-1.2.0-src.zip
      - 4b4ee3fc4e819e9ca111cfe0f2d35dc5cc270ff18b39d1a0ac0e076c80405978df0496e51eab0b0a7a887a91f6b4609c64a3bab62fcece679ea681caf9211323  apache-dolphinscheduler-incubating-1.2.0-dolphinscheduler-backend-bin.tar.gz
      - e5be814ce252e9fdf136a9473ae81ce2bf1e266e64b407535b70c424491ee5d710b89993bef3cc785afc4d7ee02b642678553101e3beaec06b091aac06cde036 apache-dolphinscheduler-incubating-1.2.0-dolphinscheduler-front-bin.tar.gz

Maven 2 staging repository:

   - https://repository.apache.org/content/repositories/staging/org/apache/dolphinscheduler/

Release Tag :

   - (Git Tag) 1.2.0

Release CommitID :

   - https://github.com/apache/incubator-dolphinscheduler/tree/18fd29f66df207bc90b9cdd40e02fe2db8f4a0ce<https://github.com/apache/incubator-dolphinscheduler/tree/7e93cc7c162b83b0d7306cb3045c3a0ed06bd880>

Keys to verify the Release Candidate :

   - http://pool.sks-keyservers.net:11371/pks/lookup?op=vindex&fingerprint=on&search=0xD82A432885E11560
corresponding to lgcareer@apache.org

Guide to build the release from source :

   - https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0-release/README.md

A vote regarding the quality of this test build will be initiated within the next couple of days.



Best regards!

—————————————
*DolphinScheduler(Incubator) *PPMC
*Zhanwei Qiao 乔占卫*

qiaozhanwei@outlook.com

Re: [ANNOUNCE]������������������Apache������������������DolphinScheduler(Incubating)������������������1.2.0������������������test������������������build������������������(round������������������3)������������������available

Posted by Justin Mclean <jm...@apache.org>.
Hi,

I suggest you look at this [1] and follow. If you need to check if can bundle some of the things that are included, in particular take a close look at the font licensing.

If you find [1] hard to follow I done a few talks on the incubator and making release that should help. Ask your mentors for help on this.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by Sheng Wu <wu...@gmail.com>.
Justin Mclean <jm...@apache.org> 于2019年12月4日周三 下午2:06写道：

>
> 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.
>

They prefer to check the feature first maybe, I think the sequence is not
required. If they want to check first, then they could do this.

I think the key of our discussion here is more about the `announcement`.
You are thinking they are doing release directly without IPMC vote. They
are not.
Do you have any place said, they should not use announcement mail, or just
in English language perspective, it is not a good one?

> Any connivance binary has to 100% match the source code in the voted on
source release.

They should for sure. But even they matched, the features could break. May
be lack of autotests, or special env requires, whatever.
I think how to test is the PPMC's choice.



>
> > 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.
>

I am not saying they are voting on binary. My point is, they are testing.



>
> 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).
>

If you have found something wrong in their source release, it will be great
to share it with PPMC. If they need another round of test and vote, then I
think they will do.



>
> Thanks,
> Justin
>

Re: Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by 李 岗 <lg...@outlook.com>.
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 李岗

lgcareer2019@outlook.com<ma...@outlook.com>

From: Justin Mclean<ma...@apache.org>
Date: 2019-12-04 14:06
To: dev@dolphinscheduler.apache.org<ma...@dolphinscheduler.apache.org>
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

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by Justin Mclean <jm...@apache.org>.
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

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by Sheng Wu <wu...@gmail.com>.
Justin Mclean <jm...@apache.org> 于2019年12月4日周三 下午12:14写道：

> Hi,
>
> > Thanks for reminder, this email is not an IPMC vote, it’s just internal
> announcements, there is another mail for DolphinScheduler ppmc vote for
> first apache release,
>
> I’m not 100% sure what you mean by an "internal announcement”. I’m
> guessing something has been lost in translation? What is the purpose of
> this test build?
>

Hi Justin

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.
Then they will use the same tar balls to do PPMC vote, then IPMC. If the
test fails, because of some serious bugs, this release process could be
canceled.
So basically, this is their first step on release process.

I think this is fine due to the team is checking the features only. I think
this `[ANNOUNCE]` as the title prefix is fine. The real tar balls have not
pushed to Maven central or svn dist folder, AFAIK.



>
> >  “ [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0 “ , It has
> passed 72 hours, and we will announce vote result later.
>
> It would need to pass an IPMC vote before it can be released. I don’t
> think that has happened?
>
> Thanks,
> Justin

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by lidong dai <da...@gmail.com>.
hi Justin,

  Yes, you are right. for now It is the DolphinScheduler community's ppmc
voting for the 1.2.0 release, and has not yet reached the step of ipmc
vote.



Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------


Justin Mclean <jm...@apache.org> 于2019年12月4日周三 下午12:14写道：

> Hi,
>
> Thanks for reminder, this email is not an IPMC vote, it’s just internal
> announcements, there is another mail for DolphinScheduler ppmc vote for
> first apache release,
>
>
> I’m not 100% sure what you mean by an "internal announcement”. I’m
> guessing something has been lost in translation? What is the purpose of
> this test build?
>
>  “ [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0 “ , It has
> passed 72 hours, and we will announce vote result later.
>
>
> It would need to pass an IPMC vote before it can be released. I don’t
> think that has happened?
>
> Thanks,
> Justin
>

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by Justin Mclean <jm...@apache.org>.
Hi,

> Thanks for reminder, this email is not an IPMC vote, it’s just internal announcements, there is another mail for DolphinScheduler ppmc vote for first apache release,

I’m not 100% sure what you mean by an "internal announcement”. I’m guessing something has been lost in translation? What is the purpose of this test build?

>  “ [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0 “ , It has passed 72 hours, and we will announce vote result later.

It would need to pass an IPMC vote before it can be released. I don’t think that has happened?

Thanks,
Justin

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by lidong dai <da...@gmail.com>.
Hi Justin,

      for now, DolphinScheduler use apache official checklist:
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist，
haha



Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------




开 2019年12月4日 在 11:45:33, lidong dai (dailidong66@gmail.com) 写到:

hi Justin,

Thanks for reminder, this email is not an IPMC vote, it’s just internal
announcements, there is another mail for DolphinScheduler ppmc vote for
first apache release,  named “ [VOTE] Release Apache DolphinScheduler
(Incubating) 1.2.0 “ , It has passed 72 hours, and we will announce vote
result later. I think we are already ready for the first apache release, we
prepared for this release nearly 4 months.  very happy to give us
suggestions.




Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------




开 2019年12月4日 在 06:47:54, Justin Mclean (jmclean@apache.org) 写到:

Hi,

I also took a look at the release and can see some issues with it, it
probably wouldn't pass an IPMC vote. When voting on a release I suggest you
use a checklist (either an existing one) or one the project makes up. [1] I
would also suggest you use the work in progress disclaimer [2] and list
anything you think may be an issue. In particular this will help with your
first release.

Thanks,
Justin

1.
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
2. https://incubator.apache.org/policy/incubation.html#disclaimers

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by lidong dai <da...@gmail.com>.
Yes，I know this, when testing, once find a bug, if need to change some
source file,  we will re-vote, and wait another 72 hours.


Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------




开 2019年12月4日 在 16:34:18, Justin Mclean (jmclean@apache.org) 写到:

Hi,

> Thanks for reminder, this email is not an IPMC vote, it’s just internal
> announcements, there is another mail for DolphinScheduler ppmc vote for
> first apache release

Yes but this mentions changes which make that other vote null and void, if
you make any changes to a release you need to take another vote and what
you are voting on can't change during the voting process.

Thanks,
Justin

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by Justin Mclean <jm...@apache.org>.
Hi,

> Thanks for reminder, this email is not an IPMC vote, it’s just internal
> announcements, there is another mail for DolphinScheduler ppmc vote for
> first apache release

Yes but this mentions changes which make that other vote null and void, if you make any changes to a release you need to take another vote and what you are voting on can't change during the voting process.

Thanks,
Justin

Re: [ANNOUNCE]Apache DolphinScheduler(Incubating) 1.2.0 test build (round 3) available

Posted by lidong dai <da...@gmail.com>.
hi Justin,

Thanks for reminder, this email is not an IPMC vote, it’s just internal
announcements, there is another mail for DolphinScheduler ppmc vote for
first apache release,  named “ [VOTE] Release Apache DolphinScheduler
(Incubating) 1.2.0 “ , It has passed 72 hours, and we will announce vote
result later. I think we are already ready for the first apache release, we
prepared for this release nearly 4 months.  very happy to give us
suggestions.




Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------




开 2019年12月4日 在 06:47:54, Justin Mclean (jmclean@apache.org) 写到:

Hi,

I also took a look at the release and can see some issues with it, it
probably wouldn't pass an IPMC vote. When voting on a release I suggest you
use a checklist (either an existing one) or one the project makes up. [1] I
would also suggest you use the work in progress disclaimer [2] and list
anything you think may be an issue. In particular this will help with your
first release.

Thanks,
Justin

1.
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
2. https://incubator.apache.org/policy/incubation.html#disclaimers

Re: [ANNOUNCE]������Apache������DolphinScheduler(Incubating)������1.2.0������test������build������(round������3)������available

Posted by Justin Mclean <jm...@apache.org>.
Hi,

I also took a look at the release and can see some issues with it, it probably wouldn't pass an IPMC vote. When voting on a release I suggest you use a checklist (either an existing one) or one the project makes up. [1] I would also suggest you use the work in progress disclaimer [2] and list anything you think may be an issue. In particular this will help with your first release.

Thanks,
Justin

1. https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
2. https://incubator.apache.org/policy/incubation.html#disclaimers

Re: [ANNOUNCE]��Apache��DolphinScheduler(Incubating)��1.2.0��test��build��(round��3)��available

Posted by Justin Mclean <jm...@apache.org>.
Hi,

I'm a little confused by this announcement, is it meant to be a [VOTE] on a release candidate? An [ANNOUNCE] is only made after teh IPMC has voted on a release.

Thanks,
Justin