Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc06
+1 (binding) - .asc, .sha512 are correct. - no unexpected binary files in src. - “incubating” in src name and doc. - files have license header if needed. - LICENSE and NOTICE exist. - didn’t compile b/c OS not supported. > On May 17, 2021, at 11:18, 寒江雪 wrote: > > Hi all, > > Please review and vote on Apache Doris 0.14.0-incubating-rc06 release. > > Apache Doris is an MPP-based interactive SQL data warehousing for reporting > and analysis. > > The Apache Doris community has voted on and approved this release: > https://lists.apache.org/thread.html/r1fd266598796a7b18ac00c7a23f8ad23ebcd0e6a64d83277f25c8150%40%3Cdev.doris.apache.org%3E > > The vote result email thread: > https://lists.apache.org/thread.html/r4d34c37304efe41b6999d4475b962b0923e39356cd200dbef045312f%40%3Cdev.doris.apache.org%3E > > The release candidate has been tagged in GitHub as 0.14.0-rc06, available > here: > https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc06 > > Thanks to everyone who has contributed to this release, and there is a > simple release notes can be found here: > https://github.com/apache/incubator-doris/issues/5374 > > The artifacts (source, signature and checksum) corresponding to this release > candidate can be found here: > https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc06 > > This has been signed with PGP key 59F2ACED, corresponding to > yang...@apache.org. > KEYS file is available here: > https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS > It is also listed here: > https://people.apache.org/keys/committer/yangzhg.asc > > The vote will be open for at least 72 hours. > [ ] +1 Approve the release > [ ] +0 No opinion > [ ] -1 Do not release this package because ... > > To verify and build, you can refer to the following wiki: > https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release > https://wiki.apache.org/incubator/Incubator+Release+Checklist > > You can also refer to instruction: > > Firstly, you must install and start docker service, and then you could > build Doris as the following steps: > > Step1: Pull the docker image with Doris building environment > $ docker pull apachedoris/doris-dev:build-env-1.2 > You can check it by listing images, its IMAGE ID is d854b488afaf > > Step2: Run the Docker image > You can run the image directly: > $ docker run -it apachedoris/doris-dev:build-env1.2 > > Step3: Download Doris source > Now you should in the docker environment, and you can download the Doris > source package. > (If you have downloaded the source, and it is not in the image, you can map > its path to the image in Step2.) > $ wget > https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc06/apache-doris-0.14.0-incubating-src.tar.gz > > Step4: Build Doris > Now you can decompress and enter Doris source path and build Doris. > $ tar -zxvf apache-doris-0.14.0-incubating-src.tar.gz > $ cd apache-doris-0.14.0-incubating-src > $ sh build.sh > > Best Regards, > Yang Zhengguo — Zhenxu Ke (柯振旭) GitHub @kezhenxu94 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Heron Release 0.20.4-incubating Release Candidate 1
Thank you to everyone who participated in the vote. The voting is now closed and it has passed. Binding votes: 1: +1 votes - Ming Wen - Kevin Ratnasekera - Justin Mclean 0 : 0 votes 0: -1 votes
Re: [VOTE] Release Apache NLPCraft - Java Client (incubating) 0.7.5
Hi, There are two important things I want to mention: 1) 72 hours have not been completed for this vote. So, let's wait for it. 2) Carrying over binding votes from dev list to general is something people have been talking about for a while now. Let's carry it into another mail thread in general. Kind Regards, Furkan KAMACI On Sun, May 23, 2021 at 7:53 AM Daniel Widdis wrote: > It seems to me that knowing who has carryover votes is not important for a > lazy consensus vote. > > The +1 votes are not really required except in the rare case they might be > needed to counter a -1; in which case I'd suggest intentional action > following the -1 would make more sense than saying "oh well, we had 4 > carryover votes so we can ignore the -1". > > On 5/22/21, 8:44 PM, "Justin Mclean" wrote: > > Hi, > > > I think that IPMC votes of Mentors must automatically carryover. > (Means the VOTE thread is clearly linked, not just RESULTS (This one was > not.)) > > IMO The IPMC members (if any) who voted on the podlings dev list need > to be clearly stated in the vote email sent to the IPMC general list. The > IPMC composition changes over time and not listing them may make it > difficult when looking at historical votes. > > Thanks, > Justin > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache NLPCraft - Java Client (incubating) 0.7.5
I have a few comments on this release process. 1. If an IPMC member has voted +1 on a release, that vote is valid regardless of which list the vote was held on. It's the bits that are important. [1] 2. For clarity, when a successful vote is held on the podling's dev list, the vote thread on the general@incubator list should summarize the vote: +1 Joe Bloe (IPMC), Sam Snade(IPMC) +1 three others (ok to list the voters or simply summarize them) [3] 3. The vote on general@incubator is not lazy. No release vote is lazy. 4. To publish a release, at least three IPMC members must vote +1 and there must be more +1 than -1 votes. [2] 5. If a vote is withdrawn because of some issue, the name of the artifacts should be changed, e.g. -RC1 should change to -RC2 and so on until a vote is successful. When moving the artifact from the staging area to the release area, the artifact names would drop the -RC terminology. [4] 6. The [VOTE] threads should not use "reply" to create the [VOTE][RESULT] message. There should be a new message with the result. This makes it easier for mail clients to accurately represent the four vote threads: vote on the dev list, vote result on the dev list, vote on the incubator list, vote result on the incubator list. 7, Every effort should be made to get all (at least three) mentors (who are all IPMC members) to vote on the release. In this case, no more votes from the incubator list need to be obtained. After the 72 hour period of review by other IPMC members, the vote can be concluded. Regards, Craig [1] http://incubator.apache.org/cookbook/#podling_releases [2] https://apache.org/foundation/voting.html#ReleaseVotes [3] http://incubator.apache.org/cookbook/#two_phase_vote_on_podling_releases [4] https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/ > On May 22, 2021, at 9:53 PM, Daniel Widdis wrote: > > It seems to me that knowing who has carryover votes is not important for a > lazy consensus vote. > > The +1 votes are not really required except in the rare case they might be > needed to counter a -1; in which case I'd suggest intentional action > following the -1 would make more sense than saying "oh well, we had 4 > carryover votes so we can ignore the -1". > > On 5/22/21, 8:44 PM, "Justin Mclean" wrote: > >Hi, > >> I think that IPMC votes of Mentors must automatically carryover. (Means the >> VOTE thread is clearly linked, not just RESULTS (This one was not.)) > >IMO The IPMC members (if any) who voted on the podlings dev list need to > be clearly stated in the vote email sent to the IPMC general list. The IPMC > composition changes over time and not listing them may make it difficult when > looking at historical votes. > >Thanks, >Justin > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > Craig Russell Member, Apache Incubator PMC apache@gmail.com
Re: [VOTE] Release Apache NuttX (Incubating) 10.1.0 [RC1]
Thanks Duo Zhang and John for your votes. We still need one more before we can release. > If it's the second case, then I agree we should fix it. I think it's rather the first option. As you described, we distribute two different repositories and when extracted the LICENSE files are found inside their respective folders. On Sat, May 22, 2021 at 12:36 AM Nathan Hartman wrote: > > On Thu, May 20, 2021 at 9:42 PM John D. Ament wrote: > > > Hi > > > > +1 binding from me, with a couple of notes: > > > > - it could be how I'm extracting your source tars, but the packages are > > ending up in a directory child to it. We typically look for the > > LICENSE/NOTICE/DISCLAIMER in the root folder. > > > Do you mean that you get: > > nuttx/LICENSE > > or > > /nuttx/LICENSE > > If it's the first case, I think that's usually desirable because otherwise > the users may untar expecting to get one folder with all the contents in > it, but end up getting a bunch of directories and files instead. When that > happens in a directory containing many other files, it creates a big mess. > Also as NuttX needs nuttx/ and apps/ to be sibling directories, it might be > confusing if there's no enclosing directory. (The apps/ distribution > provided by our project is optional and the user may substitute their own.) > > If it's the second case, then I agree we should fix it. > > What incantation are you using to extract the contents? > > More below: > > - I'm ok with the LICENSE but would like you all to fix this section at > > some point: > > > > > > uIP > > > > === > > > > > > Many lower-level networking components of NuttX derive from uIP which > > > > has a similar BSD style license: > > > > > >Copyright (c) 2001-2003, Adam Dunkels. > > > >All rights reserved. > > > > > > Rhombus Math Library > > > > > > > > > > The math library used in NuttX derives from the Rhombus OS by Nick Johnson > > > > (with many, many addtions). The Rhombus OS is/was distributed under the > > ISC > > > > license. The ISC licsense is a permissive license that allows people do > > > > anything with your code with proper attribution and without warranty. The > > > > ISC license is functionally equivalent to the BSD 2-Clause and MIT > > licenses, > > > > removing some language that is no longer necessary. > > > > > > IGMP > > > > > > > > > > IGMP support, if enabled, adds additional logic by Steve Reynolds: > > > > > > Copyright (c) 2002 CITEL Technologies Ltd. > > > > All rights reserved. > > > > > > This should ideally list out the actual license contents instead of an > > explanation of what the license is. > > > Good catch! We'll fix it. > > Thank you for your feedback, > Nathan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc06
Hi all: Thanks for voting, we still need more votes, thank you. kezhenxu94@apache 于2021年5月23日周日 下午8:30写道: > +1 (binding) > > - .asc, .sha512 are correct. > - no unexpected binary files in src. > - “incubating” in src name and doc. > - files have license header if needed. > - LICENSE and NOTICE exist. > - didn’t compile b/c OS not supported. > > > On May 17, 2021, at 11:18, 寒江雪 wrote: > > > > Hi all, > > > > Please review and vote on Apache Doris 0.14.0-incubating-rc06 release. > > > > Apache Doris is an MPP-based interactive SQL data warehousing for > reporting > > and analysis. > > > > The Apache Doris community has voted on and approved this release: > > > https://lists.apache.org/thread.html/r1fd266598796a7b18ac00c7a23f8ad23ebcd0e6a64d83277f25c8150%40%3Cdev.doris.apache.org%3E > > > > The vote result email thread: > > > https://lists.apache.org/thread.html/r4d34c37304efe41b6999d4475b962b0923e39356cd200dbef045312f%40%3Cdev.doris.apache.org%3E > > > > The release candidate has been tagged in GitHub as 0.14.0-rc06, available > > here: > > https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc06 > > > > Thanks to everyone who has contributed to this release, and there is a > > simple release notes can be found here: > > https://github.com/apache/incubator-doris/issues/5374 > > > > The artifacts (source, signature and checksum) corresponding to this > release > > candidate can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc06 > > > > This has been signed with PGP key 59F2ACED, corresponding to > > yang...@apache.org. > > KEYS file is available here: > > https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS > > It is also listed here: > > https://people.apache.org/keys/committer/yangzhg.asc > > > > The vote will be open for at least 72 hours. > > [ ] +1 Approve the release > > [ ] +0 No opinion > > [ ] -1 Do not release this package because ... > > > > To verify and build, you can refer to the following wiki: > > > https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release > > https://wiki.apache.org/incubator/Incubator+Release+Checklist > > > > You can also refer to instruction: > > > > Firstly, you must install and start docker service, and then you could > > build Doris as the following steps: > > > > Step1: Pull the docker image with Doris building environment > > $ docker pull apachedoris/doris-dev:build-env-1.2 > > You can check it by listing images, its IMAGE ID is d854b488afaf > > > > Step2: Run the Docker image > > You can run the image directly: > > $ docker run -it apachedoris/doris-dev:build-env1.2 > > > > Step3: Download Doris source > > Now you should in the docker environment, and you can download the Doris > > source package. > > (If you have downloaded the source, and it is not in the image, you can > map > > its path to the image in Step2.) > > $ wget > > > https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc06/apache-doris-0.14.0-incubating-src.tar.gz > > > > Step4: Build Doris > > Now you can decompress and enter Doris source path and build Doris. > > $ tar -zxvf apache-doris-0.14.0-incubating-src.tar.gz > > $ cd apache-doris-0.14.0-incubating-src > > $ sh build.sh > > > > Best Regards, > > Yang Zhengguo > > — > Zhenxu Ke (柯振旭) > GitHub @kezhenxu94 > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Sedona 1.0.1-incubating RC1
Hi, my +1 binding, except for file'license issue mentioned by other IPMCs. here is my checking list. [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] LICENSE, NOTICE and DISCLAIMER-WIP files are fine. [x] All files have license headers if necessary. --- Email:panj...@apache.org Juan Pan(Trista) Apache ShardingSphere Replied Message | From | Jia Yu | | Date | 05/23/2021 04:17 | | To | general | | Cc | Felix Cheung, Mohamed Sarwat, Netanel Malka, Paweł Kociński, Zongsi Zhang, jinxuanw, jbonofre, fengji...@gmail.com | | Subject | [VOTE] Release Apache Sedona 1.0.1-incubating RC1 | Dear all, I would like to start a vote for Apache Sedona 1.0.1-incubating RC1 Sedona community vote thread: https://lists.apache.org/thread.html/ra5f27cd5c9c3608205220c5d12a141c64681b7a5962785ce80fa73ec%40%3Cdev.sedona.apache.org%3E Sedona community vote result thread: https://lists.apache.org/thread.html/r7f2b0e72296a6fc10735148b05fa6a5d256ff7a24110c3b4920b2ef3%40%3Cdev.sedona.apache.org%3E Release notes: https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/release-notes.md Build instructions: https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/compile.md GitHub tag: https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.1-incubating-rc1 GPG public key to verify the Release: https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS Source code and binaries: https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/ The vote will be open for at least 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 do not release this package because... Thanks, Jia Yu
Re: [VOTE] Release Apache Sedona 1.0.1-incubating RC1
Hi folks, 1. The reason why the BSD license has "2020 - 2021 Apache Sedona" is that we took the original index.js from that BSD project and modified it to support our system. If this is not the correct way to show the authorship, could you please let me know what the best practice is? Then we will fix it in the next release. 2. Yes, the scalastyle_config.xml is copied from Scala style website. 3. In the next release, I will see if I can replace NASA HDF data with some alternative HDF data in order to avoid the legal issue. Thanks, Jia On Sun, May 23, 2021 at 7:48 PM Juan Pan wrote: > Hi, my +1 binding, except for file'license issue mentioned by other IPMCs. > > here is my checking list. > > [x] Download links are valid. > [x] Checksums and PGP signatures are valid. > [x] LICENSE, NOTICE and DISCLAIMER-WIP files are fine. > [x] All files have license headers if necessary. > > --- > Email:panj...@apache.org > Juan Pan(Trista) Apache ShardingSphere > Replied Message > From Jia Yu > Date 05/23/2021 04:17 > To general > Cc Felix Cheung , > Mohamed Sarwat , > Netanel Malka , > Paweł Kociński , > Zongsi Zhang , > jinxuanw , > jbonofre , > fengji...@gmail.com > Subject [VOTE] Release Apache Sedona 1.0.1-incubating RC1 > Dear all, > > I would like to start a vote for Apache Sedona 1.0.1-incubating RC1 > > Sedona community vote thread: > > https://lists.apache.org/thread.html/ra5f27cd5c9c3608205220c5d12a141c64681b7a5962785ce80fa73ec%40%3Cdev.sedona.apache.org%3E > > Sedona community vote result thread: > > https://lists.apache.org/thread.html/r7f2b0e72296a6fc10735148b05fa6a5d256ff7a24110c3b4920b2ef3%40%3Cdev.sedona.apache.org%3E > > Release notes: > > https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/release-notes.md > > Build instructions: > > https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/docs/download/compile.md > > GitHub tag: > > https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.1-incubating-rc1 > > GPG public key to verify the Release: > https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS > > Source code and binaries: > > https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/ > > The vote will be open for at least 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 do not release this package because... > > Thanks, > Jia Yu >