Help Verify Apache(incubating) TVM Release RC
Dear IPMC: I am sending this email to let you know that the Apache (incubating) TVM community started a formal RFC for our first apache release. Because this is our first ASF release, the community wanted to hold the release to the highest standard possible, by starting an RFC to ask everyone to verify the RC before the formal vote. While we have already gone through the common checklist(such as licenses and disclaimer), we would love to get help from IPMC members as well, if possible, to help us check if there is anything that we might be missing. Please refer to the following thread: - RFC thread https://github.com/apache/incubator-tvm/issues/4406 - Mirrored dev@ thread about the same RFC: https://lists.apache.org/thread.html/a5a4d6e43975809aebab46043d95ecd794a7d9235f078d732ab4e515@%3Cdev.tvm.apache.org%3E Thank you! TQ
[GitHub] [incubator] justinmclean merged pull request #50: [INFRA-19472] Correct the href of Incubator PMC in home page.
justinmclean merged pull request #50: [INFRA-19472] Correct the href of Incubator PMC in home page. URL: https://github.com/apache/incubator/pull/50 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] sunjincheng121 opened a new pull request #50: [INFRA-19472] Correct the href of Incubator PMC in home page.
sunjincheng121 opened a new pull request #50: [INFRA-19472] Correct the href of Incubator PMC in home page. URL: https://github.com/apache/incubator/pull/50 I found that the href of `Incubator PMC ` in the https://incubator.apache.org/ is mistake. as follows: `http://incubator.apache.org;>Incubator PMC` we should to correct it as follows: `https://incubator.apache.org/whoweare.html#the_incubator_project_management_commitee_pmc;>Incubator PMC` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Some interesting incubator stats
Hi, A little graph of podlings over time: https://drive.google.com/file/d/1dC1XP-xqgJP9bRRqAalgHO2Vi5iDkkIG/view?usp=sharing Download the file and open in a browser. If someone who actually knows how to use Apache ECcharts and javascript wants to play with this go ahead. 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 Superset (incubating) version 0.35.1
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes correct - LICENSE and NOTICE file - All source files have ASF headers - No unexpected binary files - Didn’t compile It would be nice if there was a non docker way to compile the source package. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator cookbook: Podling Releases update
Hi, +1 from me, as long as the podling dev list IPMC votes are clearly indicated in the vote mail to the incubator general list. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator cookbook: Podling Releases update
I believe that the current cookbook recommendations need an update. [1] 1. "Binding" should always refer to IPMC members' votes. This is a source of confusion for many podling communities. 2. Votes on the dev list should automatically carry over to the general list. Assuming that there is no change to the artifacts, the only reason for the dev vote not to carry over is that the voter changed their mind, which is an exception that should be documented in the general thread. 3. All votes count. All input is valuable. All votes whether on dev or incubator general should be tallied. 4. The discussion needs to include the recent DISCLAIMER-WIP changes to release protocol. Here is my proposed update: Podling Releases A podling is expected to make several software releases during incubation, that progress toward being fully conformant with the ASF Release Policy http://www.apache.org/legal/release-policy.html . A fully conformant release is expected as a condition of graduation. Podling releases must include the word "incubating" in any release file names and must include a DISCLAIMER or DISCLAIMER-WIP https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers to avoid any confusion as to the project’s status. As podlings are not yet "real" ASF projects, it is important to set expectations right. Also, voting on podling releases happens in two phases: First, the podling votes on the release on their dev mailing list. The main goal of this vote is for the podling community to practice and learn voting on releases. The vote is successful if there are at least three +1 votes from PPMC members, and more +1 votes from PPMC members than -1 votes from PPMC members. Then, if that first vote is successful, an Incubator PMC vote is held on the incubator general mailing list. This is required to make the vote an Act of the Foundation, as is required for all ASF releases. When the release manager calls for a vote on the general list, the results of the dev list vote are summarized in the vote message. All votes cast during the dev vote are carried over to the incubator general vote. In particular, IPMC Member votes including Mentor votes cast in the dev vote are binding in the general vote. And votes can be changed during the general vote; the last vote cast by any voter is considered definitive. At the conclusion of the vote, the results are announced to the general incubator list. All votes from the dev list and general list are reported, including the names and roles of the voters. The vote is successful if there are at least three +1 votes from IPMC members, and more +1 votes from IPMC members than -1 votes from IPMC members. Craig Current incubator web page: [1] Podling Releases https://incubator.apache.org/cookbook/#podling_releases A podling is expected to make several software releases during incubation, that gradually progress towards being fully conformant to the ASF Release Policy. In addition to following that policy, podling releases must include the word "incubating" in any release file names and a DISCLAIMER (TODO: link) to avoid any confusion as to the project’s status. As podlings are not "real" ASF projects yet, it is important to set expectations right. Also, voting on podling releases happens in two phases: First, the podling votes on the release on their dev mailing list, with PPMC members votes being "binding" and others being welcome to cast consultative votes. The main goal of this vote is for the podling community to practice and learn voting on releases. Then, if that first vote is successful, an Incubator PMC vote is held on the Incubator general mailing list. This is required to make the vote an Act of the Foundation, as is required for all ASF releases. Incubation mentors can optionally indicate that their votes in the first phase can be carried on to the Incubator PMC vote. If three mentors have voted this means the "three +1 votes" requirement is already fulfilled when that second vote starts, which can speed up things. Craig L Russell c...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Pinot (incubating) 0.2.0 released
Hello community, We are pleased to announce that Apache Pinot (incubating) 0.2.0 is released! Apache Pinot (incubating) is a distributed columnar storage engine that can ingest data in realtime and serve analytical queries at low latency. The release can be downloaded at: https://pinot.apache.org/download The release note is available at: https://github.com/apache/incubator-pinot/releases If you want to know more about Pinot, please visit our project website: https://pinot.apache.org Also, you are welcome to join and participate to Pinot community by subscribing to d...@pinot.apache.org Best Regards, Apache Pinot (incubating) Team *DISCLAIMER* Apache Pinot (incubating) is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Superset (incubating) version 0.35.1
Kind reminder, Thank you, Daniel Gaspar On 2019/11/21 16:44:52, dpgas...@apache.org wrote: > Hello IPMC, > > The Apache Superset (incubating) community has voted on and approved a > proposal to > release Apache Superset (incubating) version 0.35.1. > The voting thread can be found here: > https://lists.apache.org/thread.html/88800a66ec0e64c4adb15a8c40a34586d3a1b79d02a14f36feb0691f@%3Cdev.superset.apache.org%3E > > > Here are the binding +1 votes from mentors, carrying over from the podling > vote: > - Alan > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Superset (incubating) is a modern, enterprise-ready business > intelligence web application > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.1rc1/ > > Git tag for the release: > https://github.com/apache/incubator-superset/tree/0.35.1rc1 > > The Change Log for the release: > https://github.com/apache/incubator-superset/blob/0.35.1rc1/CHANGELOG.md > > public keys are available at: > > https://www.apache.org/dist/incubator/superset/KEYS > > The vote will be open for at least 72 hours or until the necessary number > of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Superset (Incubating) Team > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Removal of old incubator releases
On Fri, 22 Nov 2019 at 00:15, Justin Mclean wrote: > Hi, > > > I have a few questions: > > 1. are projects required to delete those old incubating release because > the > > projects are now TLPs ? > > More encouraged than required I think. > ok, thx. > > > 2. in the case of Joshua, even it's been a while since the project moved > > outside of Incubator, that's still the latest release hence I wonder: > > should we remove it anyway? > > Perhaps it would be good time to make a new release? > sure, we are discussing to cut a new (6.2) release. Thanks, Tommaso > > Thanks, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
