[ANNOUNCE] Release Apache ShardingSphere(incubating) 4.0.0-RC3
Hi all, We are glad to announce the release of Apache ShardingSphere(incubating) 4.0.0-RC3. Once again I would like to express my thanks to your help. ShardingSphere is an open-source ecosystem consisted of a set of distributed database middleware solutions, including 2 independent products, Sharding-JDBC & Sharding-Proxy. They both provide functions of data sharding, distributed transaction and database orchestration, applicable in a variety of situations such as Java isomorphism, heterogeneous language. Sharding-JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. It can be considered as an enhanced JDBC driver, which is fully compatible with JDBC and all kinds of ORM frameworks. Sharding-Proxy defines itself as a transparent database proxy, providing a database server that encapsulates database binary protocol to support heterogeneous languages. Download Links: https://shardingsphere.apache.org/document/current/en/downloads/ Release Notes: https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md Website: https://shardingsphere.apache.org/ ShardingSphere Resources: - Issue: https://github.com/apache/incubator-shardingsphere/issues/ - Mailing list: d...@shardingsphere.apache.org - Documents: https://shardingsphere.apache.org/document/current/ = *Disclaimer* Apache ShardingSphere (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. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [VOTE] Release Apache APISIX (Incubating) 0.9-RC1
Hi: +1 I checked the following points and tested that this version works fine with the CLI + Admin API. Checklist for reference: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] DISCLAIMER is included. [x] LICENSE and NOTICE files are good. [x] No binary file. [x] All files have license headers if necessary. On Thu, Nov 21, 2019 at 8:00 AM Justin Mclean wrote: > Hi, > > Just a not that this release already have 3 IPMC votes: > - Justin Mclean > - Willem Jiang > - Kevin Ratnasekera > > Thanks, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
[RESULT] [VOTE] Release Apache Pinot (incubating) 0.2.0 RC0
Thank you for everyone who participated to the vote. The voting is now closed and it has passed with four +1 (binding), and no 0 or -1 votes. Binding: +1 Felix Cheung +1 Olivier Lamy +1 Jean-Baptiste Onotre (binding) +1 Kishore Gopalakrishna Voting thread: https://lists.apache.org/thread.html/77c834b865753bbdefd3ce402738576c35c7a89a73e8992d392ae59b@%3Cgeneral.incubator.apache.org%3E Thanks, Apache Pinot (incubating) community - 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, > 1) the number of podlings entering has dropped dramatically. Some of that > drop is probably really good, but this drop is extreme. This could be > github effect or could be that Apache is viewed as old fuddy-duddies. Can't > tell from the data, but I bet everybody has an opinion, warranted or not. Re the "this drop is extreme”, another way of looking at it is that 2015 and 2016 we accepted too many projects and are still trying to digest them :-) A trend line through all of the data is still increasing upwards over time. But let's go with a decrease in the last couple of year. It’s hard to tell why from the data alone. I think this is from a number of factors: - We have been “rejecting” more projects - Other options for project exists that didn’t before and we don’t actively encourage projects to join us - The Incubator mentor carrying capacity is near it’s limit, it was over it’s limit a few years ago - We have issues around diversity and are less attractive place to some projects to be because of that - Some difficultly with adopting to modern workflows > 2) the mean and max times to incubate were goofy 10 years ago. We have no > evidence that the maximum has gotten much better since we still have some > very old podlings hanging around, but I feel like the median is a bit > better. One of the changes from about 10 years ago have a shift from projects sponsoring projects to the incubator sponsoring them. > 3) the minimum time to incubate has definitely increased over the last 10 > years. That might be due to the presence of the direct-to-TLP process. Graphing the numbers Im not seeing that at all and it’s mostly the same. Given very few project gave gone direct to TLP I wouldn’t expect this to have much of an impact. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[MENTORS] Incubator PMC report for December 2019
Hi, Here’s the schedule for next month report: Wed December 04 Podling reports due by end of day Sun December 08 Shepherd reviews due by end of day Sun December 08 Summary due by end of day Tue December 10 Mentor signoff due by end of day Wed December 11 Report submitted to Board Wed December 18 Board meeting You can fill in your report on the incubator wiki page. [1] NOTICE - A need trademark / branding question has been added, so please take care not to copy and past a previous report and forget to answer this questions. Podlings expected to report this month: APISIX BatchEE Brpc Crail Daffodil DolphinScheduler Druid Hivemall IoTDB Marvin-AI MesaTEE Nemo Samoa Shardingsphere Spot Streampipes Superset Warble Thanks, Justin 1. https://cwiki.apache.org/confluence/display/INCUBATOR/December2019 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Some interesting incubator stats
Here is the same data in tabular form, courtesy of python and R. startYear started finished min mean median max 1 2003 14 14 58 days 653.4286 days 329.0 days 2419 days 2 2004 16 16 0 days 587.9375 days 341.5 days 2227 days 3 2005 18 18 0 days 528. days 582.5 days 989 days 4 2006 20 20 129 days 620.8500 days 463.0 days 1485 days 5 2007 11 11 196 days 754.1818 days 647.0 days 2132 days 6 2008 19 19 281 days 1156.8421 days 1270.0 days 2579 days 7 2009 14 14 102 days 735.2857 days 545.5 days 1836 days 8 2010 22 22 282 days 842.5455 days 731.5 days 2599 days 9 2011 27 27 126 days 580.4815 days 436.0 days 2675 days 10 2012 14 14 154 days 715.6429 days 531.0 days 1794 days 11 2013 23 22 161 days 571.3182 days 448.5 days 1619 days 12 2014 19 16 233 days 629.9375 days 487.5 days 1508 days 13 2015 30 25 183 days 623.0400 days 584.0 days 1468 days 14 2016 30 23 303 days 713.6087 days 673.0 days 1348 days 15 2017 155 329 days 505. days 485.0 days 741 days 16 2018 142 294 days 373.5000 days 373.5 days 453 days 17 201990 Inf days NaN days NA days -Inf days I see a few prominent things: 1) the number of podlings entering has dropped dramatically. Some of that drop is probably really good, but this drop is extreme. This could be github effect or could be that Apache is viewed as old fuddy-duddies. Can't tell from the data, but I bet everybody has an opinion, warranted or not. 2) the mean and max times to incubate were goofy 10 years ago. We have no evidence that the maximum has gotten much better since we still have some very old podlings hanging around, but I feel like the median is a bit better. 3) the minimum time to incubate has definitely increased over the last 10 years. That might be due to the presence of the direct-to-TLP process. On Thu, Nov 21, 2019 at 2:31 PM Justin Mclean wrote: > Hi, > > Whimsey also provides that data as JSON [1], I put together a little > python script to generate these stats: > > Total podlings: 315 > Total retired podlings: 61 > Total graduated podlings: 207 > Total current podlings: 47 > > From 14 poddings that joined in 2003 10 graduated, 4 retired and 0 are > incubating. > From 16 poddings that joined in 2004 13 graduated, 3 retired and 0 are > incubating. > From 18 poddings that joined in 2005 13 graduated, 5 retired and 0 are > incubating. > From 20 poddings that joined in 2006 15 graduated, 5 retired and 0 are > incubating. > From 11 poddings that joined in 2007 7 graduated, 4 retired and 0 are > incubating. > From 19 poddings that joined in 2008 12 graduated, 7 retired and 0 are > incubating. > From 14 poddings that joined in 2009 12 graduated, 2 retired and 0 are > incubating. > From 22 poddings that joined in 2010 17 graduated, 5 retired and 0 are > incubating. > From 27 poddings that joined in 2011 23 graduated, 4 retired and 0 are > incubating. > From 14 poddings that joined in 2012 11 graduated, 3 retired and 0 are > incubating. > From 23 poddings that joined in 2013 19 graduated, 3 retired and 1 are > incubating. > From 19 poddings that joined in 2014 13 graduated, 3 retired and 3 are > incubating. > From 30 poddings that joined in 2015 20 graduated, 5 retired and 5 are > incubating. > From 30 poddings that joined in 2016 17 graduated, 6 retired and 7 are > incubating. > From 15 poddings that joined in 2017 4 graduated, 1 retired and 10 are > incubating. > From 14 poddings that joined in 2018 1 graduated, 1 retired and 12 are > incubating. > From 9 poddings that joined in 2019 0 graduated, 0 retired and 9 are > incubating. > > Thanks, > Justin > > 1. https://whimsy.apache.org/public/public_podlings.json > - > 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
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. > 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? Thanks, Justin - 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, For a podling exit point of view: From 1 poddings that exited in 2003 1 graduated, 0 retired. From 10 poddings that exited in 2004 9 graduated, 1 retired. From 12 poddings that exited in 2005 11 graduated, 1 retired. From 11 poddings that exited in 2006 6 graduated, 5 retired. From 24 poddings that exited in 2007 17 graduated, 7 retired. From 9 poddings that exited in 2008 7 graduated, 2 retired. From 10 poddings that exited in 2009 7 graduated, 3 retired. From 14 poddings that exited in 2010 12 graduated, 2 retired. From 11 poddings that exited in 2011 6 graduated, 5 retired. From 40 poddings that exited in 2012 33 graduated, 7 retired. From 21 poddings that exited in 2013 20 graduated, 1 retired. From 19 poddings that exited in 2014 17 graduated, 2 retired. From 18 poddings that exited in 2015 12 graduated, 6 retired. From 14 poddings that exited in 2016 12 graduated, 2 retired. From 25 poddings that exited in 2017 19 graduated, 6 retired. From 18 poddings that exited in 2018 9 graduated, 9 retired. From 11 poddings that exited in 2019 9 graduated, 2 retired. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Omid and Tephra - Graduation (or Retirement?)
Hi, I think I would call a project that exited the incubator, but still at the ASF with a community around it and PMC oversight. a success. It didn’t graduate as a TLP, and nor was it sponsored by the project it ended up it just took a different path. Thanks, Justin - 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, Whimsey also provides that data as JSON [1], I put together a little python script to generate these stats: Total podlings: 315 Total retired podlings: 61 Total graduated podlings: 207 Total current podlings: 47 From 14 poddings that joined in 2003 10 graduated, 4 retired and 0 are incubating. From 16 poddings that joined in 2004 13 graduated, 3 retired and 0 are incubating. From 18 poddings that joined in 2005 13 graduated, 5 retired and 0 are incubating. From 20 poddings that joined in 2006 15 graduated, 5 retired and 0 are incubating. From 11 poddings that joined in 2007 7 graduated, 4 retired and 0 are incubating. From 19 poddings that joined in 2008 12 graduated, 7 retired and 0 are incubating. From 14 poddings that joined in 2009 12 graduated, 2 retired and 0 are incubating. From 22 poddings that joined in 2010 17 graduated, 5 retired and 0 are incubating. From 27 poddings that joined in 2011 23 graduated, 4 retired and 0 are incubating. From 14 poddings that joined in 2012 11 graduated, 3 retired and 0 are incubating. From 23 poddings that joined in 2013 19 graduated, 3 retired and 1 are incubating. From 19 poddings that joined in 2014 13 graduated, 3 retired and 3 are incubating. From 30 poddings that joined in 2015 20 graduated, 5 retired and 5 are incubating. From 30 poddings that joined in 2016 17 graduated, 6 retired and 7 are incubating. From 15 poddings that joined in 2017 4 graduated, 1 retired and 10 are incubating. From 14 poddings that joined in 2018 1 graduated, 1 retired and 12 are incubating. From 9 poddings that joined in 2019 0 graduated, 0 retired and 9 are incubating. Thanks, Justin 1. https://whimsy.apache.org/public/public_podlings.json - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Omid and Tephra - Graduation (or Retirement?)
Ok my mistake about Solr. I thought it was a TLP. As to the second half of what I said still this doesn’t look like a failure to gain a community and stable management. Omid and Tephra code is now under Phoenix. The Phoenix TLP has a community and stable management. Just like Lucene has a community and stable management. > On Nov 21, 2019, at 5:16 PM, Dave Fisher wrote: > > > > Sent from my iPhone > >> On Nov 21, 2019, at 2:10 PM, Andrew Purtell wrote: >> >> Those aren’t comparable though, right? >> >> Solr was a sub project that graduated to a TLP. > > Solr is a sub project of Lucene. >> >> Omid and Tephra are projects that instead of becoming TLP’s “graduated” into >> the existing Phoenix TLP. >> >> Not the same thing. > > Exactly. >> >> And also I don’t believe this result is unsuccessful. Neither Omid or Tephra >> code bases are read only or discarded. Omid and Tephra past or future >> contributors still have a code base and community to work with. Past Omid >> and Tephra committers can become Phoenix committers. Phoenix is a stable >> TLP. This looks like a success. >> >> On Nov 21, 2019, at 4:55 PM, Dave Fisher wrote: >>> >>> Hi Justin, >>> > On Nov 21, 2019, at 1:48 PM, Justin Mclean > wrote: HI, > I’m going to change podlings.xml to reflect these as “graduated”. If > after discussion we have consensus to change these to “retired” then the > change is easy. To officially graduate that would need a board proposal would it not? >>> >>> To graduate as a TLP yes. To graduate as a subproject of an existing TLP >>> no. [1] >>> >>> So there are two kinds of graduation as a subproject: successful like Solr, >>> DistributedLog, … and unsuccessful like Omid and Tephra. Certainly the >>> “success” here is hard to measure. Your analysis in the future should >>> consider the resolution tag which has 'https://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project >>> Thanks, Justin - 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 >>> >> >> - >> 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Omid and Tephra - Graduation (or Retirement?)
Sent from my iPhone > On Nov 21, 2019, at 2:10 PM, Andrew Purtell wrote: > > Those aren’t comparable though, right? > > Solr was a sub project that graduated to a TLP. Solr is a sub project of Lucene. > > Omid and Tephra are projects that instead of becoming TLP’s “graduated” into > the existing Phoenix TLP. > > Not the same thing. Exactly. > > And also I don’t believe this result is unsuccessful. Neither Omid or Tephra > code bases are read only or discarded. Omid and Tephra past or future > contributors still have a code base and community to work with. Past Omid and > Tephra committers can become Phoenix committers. Phoenix is a stable TLP. > This looks like a success. > > >> On Nov 21, 2019, at 4:55 PM, Dave Fisher wrote: >> >> Hi Justin, >> On Nov 21, 2019, at 1:48 PM, Justin Mclean wrote: >>> >>> HI, >>> I’m going to change podlings.xml to reflect these as “graduated”. If after discussion we have consensus to change these to “retired” then the change is easy. >>> >>> To officially graduate that would need a board proposal would it not? >> >> To graduate as a TLP yes. To graduate as a subproject of an existing TLP no. >> [1] >> >> So there are two kinds of graduation as a subproject: successful like Solr, >> DistributedLog, … and unsuccessful like Omid and Tephra. Certainly the >> “success” here is hard to measure. Your analysis in the future should >> consider the resolution tag which has 'https://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project >> >>> >>> Thanks, >>> Justin >>> - >>> 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 >> > > - > 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: [DISCUSS] Omid and Tephra - Graduation (or Retirement?)
Those aren’t comparable though, right? Solr was a sub project that graduated to a TLP. Omid and Tephra are projects that instead of becoming TLP’s “graduated” into the existing Phoenix TLP. Not the same thing. And also I don’t believe this result is unsuccessful. Neither Omid or Tephra code bases are read only or discarded. Omid and Tephra past or future contributors still have a code base and community to work with. Past Omid and Tephra committers can become Phoenix committers. Phoenix is a stable TLP. This looks like a success. > On Nov 21, 2019, at 4:55 PM, Dave Fisher wrote: > > Hi Justin, > >> On Nov 21, 2019, at 1:48 PM, Justin Mclean wrote: >> >> HI, >> >>> I’m going to change podlings.xml to reflect these as “graduated”. If after >>> discussion we have consensus to change these to “retired” then the change >>> is easy. >> >> To officially graduate that would need a board proposal would it not? > > To graduate as a TLP yes. To graduate as a subproject of an existing TLP no. > [1] > > So there are two kinds of graduation as a subproject: successful like Solr, > DistributedLog, … and unsuccessful like Omid and Tephra. Certainly the > “success” here is hard to measure. Your analysis in the future should > consider the resolution tag which has 'https://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project > >> >> Thanks, >> Justin >> - >> 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Omid and Tephra - Graduation (or Retirement?)
Hi Justin, > On Nov 21, 2019, at 1:48 PM, Justin Mclean wrote: > > HI, > >> I’m going to change podlings.xml to reflect these as “graduated”. If after >> discussion we have consensus to change these to “retired” then the change is >> easy. > > To officially graduate that would need a board proposal would it not? To graduate as a TLP yes. To graduate as a subproject of an existing TLP no. [1] So there are two kinds of graduation as a subproject: successful like Solr, DistributedLog, … and unsuccessful like Omid and Tephra. Certainly the “success” here is hard to measure. Your analysis in the future should consider the resolution tag which has 'https://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project > > Thanks, > Justin > - > 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: [DISCUSS] Omid and Tephra - Graduation (or Retirement?)
HI, > I’m going to change podlings.xml to reflect these as “graduated”. If after > discussion we have consensus to change these to “retired” then the change is > easy. To officially graduate that would need a board proposal would it not? 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 Pinot (incubating) 0.2.0 RC0
+1 Thanks, KIshore G On Wed, Nov 20, 2019 at 8:48 PM Jean-Baptiste Onofré wrote: > +1 (binding) > > Regards > JB > > On 18/11/2019 20:35, Subbu Subramaniam wrote: > > Hi all, > > > > This is a call for vote to the release Apache Pinot (incubating) version > > 0.2.0. > > > > Apache Pinot (incubating) is a distributed columnar storage engine that > can > > ingest data in realtime and serve analytical queries at low latency. > > > > Pinot community has voted and approved this release. > > > > Vote threads: > > > https://lists.apache.org/thread.html/302ea5dd91e731eaaf9ce3881e027613ebc76a8c01472c0517b56e89@%3Cdev.pinot.apache.org%3E > > > https://lists.apache.org/thread.html/3d785c502905b23f1d4d1da8718501a7cb4ef8245dd665fe99bf6daf@%3Cdev.pinot.apache.org%3E > > > > Result thread: > > > https://lists.apache.org/thread.html/c425825f7d9da198adfbc5c5633dd0300f77f0ce3f9b88dba92dbe60@%3Cdev.pinot.apache.org%3E > > > > The release candidate: > > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.2.0-rc0 > > > > Git tag for this release: > > https://github.com/apache/incubator-pinot/tree/release-0.2.0-rc0 > > > > Git hash for this release: > > f8e1980c4160ac7fd2686d9edefab9ac0a825c5b > > > > The artifacts have been signed with key: B530034C, which can be > > found in the following KEYS file. > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > Release notes: > > https://github.com/apache/incubator-pinot/releases/tag/release-0.2.0-rc0 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachepinot-1003 > > > > Documentation on verifying a release candidate: > > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly, > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > > > -Subbu Subramaniam > > (on behalf of Apache Pinot (incubating) team) > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[DISCUSS] Omid and Tephra - Graduation (or Retirement?)
Hi - We are calling the movement of Omid and Tephra graduation to a project. To me this looks more like retirement where a podling moves on to a new place after failing to incubate. This distinction makes no difference to the podling. It does matter to the Incubator as we measure our success in Incubating projects. I’m going to change podlings.xml to reflect these as “graduated”. If after discussion we have consensus to change these to “retired” then the change is easy. Thoughts? Regards, Dave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] DataSketches Memory 1.2.0-incubating released!
Hello All, 1. The Apache DataSketches Memory 1.2.0-incubating has been released! NOTE 1: This component of the DataSketches library provides high-performance access to off-heap memory for Java applications. These are low-level functions that are used by other DataSketches components. It does not provide any command-line interface or GUI. Voting: Thread Permalink: https://lists.apache.org/thread.html/47438799939833b0fabb701ee6425e5e637c53b09341dee5392cc410@%3Cgeneral.incubator.apache.org%3E PPMC Round1 : 3 binding (+1) votes: Dave Fisher, Kenneth Knowles, Furkan Kamaci; 1 non-binding (+1) vote: Alexandar Saydakov IPMC Round2 : 4 binding (+1) votes: Dave Fisher, Keneth Knowles, Justin Mclean, Furkan Kamaci 2. Source repository: - https://github.com/apache/incubator-datasketches-memory Git Tag for this release: - https://github.com/apache/incubator-datasketches-memory/tree/1.2.0-incubating on branch 1.2.X-incubating Git HashId for this release starts with: 76038e8 3. Dist/release: https://dist.apache.org/repos/dist/release/incubator/datasketches/memory/1.2.0-incubating/ 4. Nexus: https://repository.apache.org/content/repositories/releases/org/apache/datasketches/datasketches-memory/1.2.0-incubating/ 5. Download, build, test and documentation: https://github.com/apache/incubator-datasketches-memory/blob/master/README.md Thank you to the IPMC members and community for taking the time to review and provide guidance on our release! On behalf of the Apache DataSketches Community, = *Disclaimer* Apache DataSketches (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.
[VOTE] Release Apache Superset (incubating) version 0.35.1
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
[RESULT] [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Hi All, Release vote for Release Apache ShardingSphere (Incubating) 4.0.0-RC3 has PASSED and closed now. The results are as follows: [4] +1 Binded votes - Jean-Baptiste Onofré - Justin Mclean - Gosling Von - Sheng Wu [ 0 ] +0 Binded Votes [ 0 ] -1 Binded Votes Thanks for everyone, especially for IPMCs who checked and voted to help this version released. I will process to publish the release andsend ANNOUNCE later. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
Yep, i missed it, thanks. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/21/2019 20:12，Ming Wen wrote： A link of the ASF code of conduct has been added to our code of conduct page [2]. However, i also want to plead you to confirm whether this link[3] is what you mentioned. I think you'd better also add the link of ASF code of conduct in Github: https://github.com/apache/incubator-shardingsphere/blob/4.0.0-RC3/CODE_OF_CONDUCT.md Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Juan Pan 于2019年11月21日周四 下午1:06写道： Hi Justin, Very appreciated your detailed checking. An issue[1] based on your suggestions was created and would be done before next release. You might want to add a link the ASF code of conduct in your code of conduct. A link of the ASF code of conduct has been added to our code of conduct page [2]. However, i also want to plead you to confirm whether this link[3] is what you mentioned. Thanks. [1] https://github.com/apache/incubator-shardingsphere/issues/3566 [2] https://shardingsphere.apache.org/community/en/contribute/code-conduct [3] https://www.apache.org/foundation/policies/conduct.html Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/21/2019 08:48，Justin Mclean wrote： Hi, +1 (binding) In the source release I checked: - incubating in name - signatures and hashes fine - DISCLAIMER exists - LICENSE and NOTICE fine - all files have ASF headers - no unexpected binary files - can compile from source A couple of suggestions: - You might want to add a link the ASF code of conduct in your code of conduct. - You might want to update your version of the Mavin wrapper to be the latest. - Something been to have gone wrong with the footer in [1] where is says "Copyright © The Apache Software Foundation, Licensed under the Apache License, Version 4.0.0-RC3”. Do you mean Apache License version 2? Thanks, Justin 1. ./sharding-ui/sharding-ui-frontend/src/components/Footer/index.vue - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
> A link of the ASF code of conduct has been added to our code of conduct page [2]. However, i also want to plead you to confirm whether this link[3] is what you mentioned. I think you'd better also add the link of ASF code of conduct in Github: https://github.com/apache/incubator-shardingsphere/blob/4.0.0-RC3/CODE_OF_CONDUCT.md Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Juan Pan 于2019年11月21日周四 下午1:06写道： > Hi Justin, > > > Very appreciated your detailed checking. > > > An issue[1] based on your suggestions was created and would be done before > next release. > > > > You might want to add a link the ASF code of conduct in your code of > conduct. > A link of the ASF code of conduct has been added to our code of conduct > page [2]. However, i also want to plead you to confirm whether this link[3] > is what you mentioned. > > > Thanks. > > > [1] https://github.com/apache/incubator-shardingsphere/issues/3566 > [2] https://shardingsphere.apache.org/community/en/contribute/code-conduct > [3] https://www.apache.org/foundation/policies/conduct.html > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 11/21/2019 08:48，Justin Mclean wrote： > Hi, > > +1 (binding) > > In the source release I checked: > - incubating in name > - signatures and hashes fine > - DISCLAIMER exists > - LICENSE and NOTICE fine > - all files have ASF headers > - no unexpected binary files > - can compile from source > > A couple of suggestions: > - You might want to add a link the ASF code of conduct in your code of > conduct. > - You might want to update your version of the Mavin wrapper to be the > latest. > - Something been to have gone wrong with the footer in [1] where is says > "Copyright © The Apache Software Foundation, Licensed under the Apache > License, Version 4.0.0-RC3”. Do you mean Apache License version 2? > > Thanks, > Justin > > 1. ./sharding-ui/sharding-ui-frontend/src/components/Footer/index.vue > - > 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
Hi Justin, all, I have a few questions: 1. are projects required to delete those old incubating release because the projects are now TLPs ? 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 ? Thanks and regards, Tommaso On Sun, 17 Nov 2019 at 11:34, Neil C Smith wrote: > On Sat, 16 Nov 2019, 23:49 Justin Mclean, > wrote: > > > It looks like you have some old incubator releases here: > > https://dist.apache.org/repos/dist/release/incubator/ > > > > We’re cleaning up the release area and it would be great if you can > remove > > these old releases. > > > > If you mean NetBeans 11.0, this is not an old release. It's the current LTS > release until next April, so left there deliberately. > > Best wishes, > > Neil > > > >
