Hi,
> /dist/release/incubator/projectxxx May be needed in the short term when a
> project just graduated and no available or stable release after being TLP
> in the short term.
Which is not teh case for any of the projects here :-)
Thanks,
Justin
Hi
/dist/release/incubator/projectxxx May be needed in the short term when a
project just graduated and no available or stable release after being TLP
in the short term.
I suggest we set up a timeline for keeping them in /dist/release/incubator,
and require the PMC team to finish their TLP
Hi,
> Ha! The Infra team was just talking about that today, with the retirement
> of Edgent and (cleanup of) Zipkin. Over the years, we've had mixed signals
> about what to do with "Incubator releases" after a podling leaves the
> Incubator. Some have said "keep them; they are IPMC releases", or
Ha! The Infra team was just talking about that today, with the retirement
of Edgent and (cleanup of) Zipkin. Over the years, we've had mixed signals
about what to do with "Incubator releases" after a podling leaves the
Incubator. Some have said "keep them; they are IPMC releases", or "they
should
Interesting data help me learn more about incubator stats.
Thanks for your detailed numbers.
Juan Pan
panj...@apache.org
Juan Pan(Trista), Apache ShardingSphere
On 11/15/2019 10:02, Justin Mclean wrote:
Hi,
Here’s some interesting incubator stats:
- Of the 315 projects that have gone
Hi All,
Voting for the Apache Heron (Incubating) 0.20.2 Release Candidate 1 has
closed.
The votes have been counted and the results are as follows:
[ 3 ] +1 - Binded Votes
- Dave Fisher
- Justin Mclean
- Furkan KAMACI
[ 0 ] +/- Binded Votes
[ 0 ] -1 Binded Votes.
Thank you for everyone's
+1. Please go ahead.
Thanks,
Junping
Justin Mclean 于2019年11月15日周五 上午7:56写道：
> Hi,
>
> If there is no objection, in a few days, I'm going to remove the following
> directories for the incubator release area, as the project have either
> graduated or retired:
>
> If a product want to remove
Great job, Justin! We need more insights like this to see how our podlings
going.
Thanks,
Junping
Justin Mclean 于2019年11月15日周五 上午10:02写道：
> Hi,
>
> Here’s some interesting incubator stats:
> - Of the 315 projects that have gone through the incubator 205 have
> graduated, 61 have retired and
HI,
> - Of the podlings that joined in 2017 4 have graduated and 1 has retired
Will do.
BTW you can generate that via the command line easily enough:
$ grep "status=" podlings.xml | grep 'startdate="2017' | wc
15 951725
$ grep "status=\"retir" podlings.xml | grep
HI,
> Please provide both median and mean values. I looked at Chinese podlings for
> my talk at COSCon 2019. The median was less than the mean due to the pull
> from projects taking a long time.
The median would be less than the mean as you note. The median is 1.4 years to
gradate and 1.3
Nice to see, thanks!
If you automate this or do it again I’d like to see e.g. …
- Of the podlings that joined in 2017 4 have graduated and 1 has retired
Thanks again
David Jencks
> On Nov 14, 2019, at 6:02 PM, Justin Mclean wrote:
>
> Hi,
>
> Here’s some interesting incubator stats:
> -
Hi Justin,
This is great information. Thanks!
Please provide both median and mean values. I looked at Chinese podlings for my
talk at COSCon 2019. The median was less than the mean due to the pull from
projects taking a long time.
Your numbers do look similar.
These are important numbers.
Interesting stats. Thanks for sharing this.
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
Justin Mclean 于2019年11月15日周五 上午10:02写道：
> Hi,
>
> Here’s some interesting incubator stats:
> - Of the 315 projects
Hi,
Here’s some interesting incubator stats:
- Of the 315 projects that have gone through the incubator 205 have graduated,
61 have retired and 49 are currently undergoing graduation.
- That means that overall 77% of projects graduate. The ones that do not do so
for a wide variety of reasons
Hi,
If there is no objection, in a few days, I'm going to remove the following
directories for the incubator release area, as the project have either
graduated or retired:
If a product want to remove this themselves, before I get to it, please go
ahead.
Yeah. Thanks.
On Thu, Nov 14, 2019 at 9:41 AM Dave Fisher wrote:
> Hi -
>
> I failed on Catalina as well. It was in bazel_configure.py due to Xcode
> now identifies as:
>
> FAILED: Could not determine the version of /usr/bin/clang from the
> following output
> /usr/bin/clang --version
> Apple
Yeah. We will fix it.
On Thu, Nov 14, 2019 at 9:41 AM Dave Fisher wrote:
> Hi -
>
> I failed on Catalina as well. It was in bazel_configure.py due to Xcode
> now identifies as:
>
> FAILED: Could not determine the version of /usr/bin/clang from the
> following output
> /usr/bin/clang --version
Dave,
We will make a note of it. Thank you for the vote as well.
- Josh
On Thu, Nov 14, 2019 at 11:41 AM Dave Fisher wrote:
> Hi -
>
> I failed on Catalina as well. It was in bazel_configure.py due to Xcode
> now identifies as:
>
> FAILED: Could not determine the version of /usr/bin/clang
Hi -
I failed on Catalina as well. It was in bazel_configure.py due to Xcode now
identifies as:
FAILED: Could not determine the version of /usr/bin/clang from the following
output
/usr/bin/clang --version
Apple clang version 11.0.0 (clang-1100.0.33.12)
Target: x86_64-apple-darwin19.0.0
Thread
Thanks for sending Furkan. Bazel has an aggressive release schedule with
breaking changes between versions. Bazel recently jumped from ~.0.2x.x to
version 1.x that offers stability for up to 3 months at a time. The
build rules specified for version 0.26.0 are not compatible with 1.1.0. We
have
Hi,
Babel info is as follows:
brew info bazel
bazel: stable 1.1.0 (bottled)
Google's own build tool
https://bazel.build/
/usr/local/Cellar/bazel/1.1.0 (11 files, 25.8MB) *
Poured from bottle on 2019-11-14 at 18:07:21
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/bazel.rb
Ning,
The current Travis CI script runs with Bazel 0.26.0.
On Thu, Nov 14, 2019 at 11:13 AM Ning Wang wrote:
> Which version of bazel you are using? Heron is using 0.26.1 current.
>
> Mac dev environment could be another possibility. XCode tool chain seems to
> have some changes causing some
Which version of bazel you are using? Heron is using 0.26.1 current.
Mac dev environment could be another possibility. XCode tool chain seems to
have some changes causing some rules to fail and maybe the new MacOS has
these changes by default. I have been using docker to build after
installing
Hi -
Carrying over my +1 (binding) from the dev@heron thread.
Regards,
Dave
> On Nov 10, 2019, at 6:49 AM, Josh Fischer wrote:
>
> Hi,
>
> The Apache Heron community has voted and approved the proposal to
> release Apache Heron (Incubating) version 0.20.2-rc1. We request the
> IPMC members
I'm a bit confused about where we go from this point.
Given the doc[1] that Alan shared last time, we are good to move ahead
with the logistical changes.
Further, the next guide[2] simply says that VP Phoenix (me) should
coordinate with VP Incubator.
Should I go ahead and file the TLP
Hi,
+1 from me.
I checked:
- Incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
PS 1: Justin's objections should be resolved.
PS 2: I couldn't compile the source code at my MacOSX Catalina following
Hi all,
We have one binding vote so far. Does anyone have the time to vote on this
release?
- Josh
On Sun, Nov 10, 2019 at 2:42 PM Justin Mclean
wrote:
> Hi,
>
> +1 (binding)
>
> Thanks for fixing teh issues raised last time.
>
> I checked:
> - incubating in name
> - signatures and hashes
27 matches
Mail list logo
