Fwd: [apache/incubator-zipkin-website] Bump nokogiri from 1.10.3 to 1.10.5 (#20)

rainy day task for anyone watching a movie they watched already and there's a scene that you're too lazy to fast forward to, but not too lazy to open a ticket with apache to delete our old website content :D -- Forwarded message - From: dependabot[bot] Date: Fri, Nov 1, 2019 at 8:

Re: Plan to revert back to OpenZipkin

, else they wouldn't have called it > AC> out. > > AC> Regardless, I added it to the tracking issue. > AC> https://github.com/apache/incubator-zipkin/issues/2629 > AC> -A > > AC> On Mon, Jun 17, 2019 at 12:30 PM Adrian Cole > wrote: > > >&g

Re: Plan to revert back to OpenZipkin

if one will. As this was called out, I expect it to be one of those higher priority type of paperwork, else they wouldn't have called it out. Regardless, I added it to the tracking issue. https://github.com/apache/incubator-zipkin/issues/2629 -A On Mon, Jun 17, 2019 at 12:30 PM Adrian Cole

Re: Plan to revert back to OpenZipkin

t 10:00 AM Adrian Cole wrote: > > Here's the more important INFRA task for the revert > https://issues.apache.org/jira/browse/INFRA-18604 > > Mentors, if there is any fear or confusion that would stall or stress > our exit, please help support. Hopefully, there will be none. &g

Re: [RESULT] [VOTE] Withdraw from the Apache Incubator

Apologies for the typo: this PASSED with 10 (+1 binding) votes, not 8. On Mon, Jun 17, 2019 at 12:18 PM Adrian Cole wrote: > > Thanks to everyone that participated. The vote to withdraw from the > Apache Incubator is now closed. It PASSED with 8 (+1 binding) votes > and no 0 or -1

[RESULT] [VOTE] Withdraw from the Apache Incubator

Thanks to everyone that participated. The vote to withdraw from the Apache Incubator is now closed. It PASSED with 8 (+1 binding) votes and no 0 or -1 votes. There were non-binding results: 2 (+1) votes and no 0 or -1 votes. Binding votes: IPMC +2 Sheng Wu, Willem Jiang PPMC +8 Adrian Cole, Bas

we've been asked to vote again...

Hi, team. We have been asked to revote on the apache dev list to leave Apache. If you hadn't voted before, or want to re-affirm or revise your opinion, please vote here, now a public list https://lists.apache.org/thread.html/5901f86d548661aaeda0af3f438686923c310248ed24d73f3222938d@%3Cdev.zipkin.a

Re: [VOTE] Withdraw from the Apache Incubator

+1 On 2019/06/14 02:24:56, Adrian Cole wrote: > The PPMC held a vote on our private list to withdraw from the Apache > Incubator. We did this for reason of discretion, similar to how new > PPMC members are voted in, and for lack of any formal process to > conduct such a vote. J

[VOTE] Withdraw from the Apache Incubator

", so this vote is in accordance with that request. 8 votes to leave carry over from the private list, including 7 of our 12 PPMC members [1]. There were no 0 or -1 votes cast. IPMC +1 Sheng Wu PPMC +7 Adrian Cole, Bas van Beek, José Carlos Chávez, Kristof Adriaenssens, Jorge Esteban Quil

Re: Plan to revert back to OpenZipkin

Here's the more important INFRA task for the revert https://issues.apache.org/jira/browse/INFRA-18604 Mentors, if there is any fear or confusion that would stall or stress our exit, please help support. Hopefully, there will be none. Best, -Adrian On Thu, Jun 13, 2019 at 9:42 AM Adrian

Re: [RESULT] [VOTE] Withdraw from the Apache Incubator

As promised, here is the email thread detailing the plan to revert https://lists.apache.org/thread.html/8d8f85b898ae6e6ac79376a88d292babf69b1a1e4365c2a674b68db4@%3Cdev.zipkin.apache.org%3E On 2019/06/13 01:17:40, Adrian Cole wrote: > The Zipkin team conducted a 7 day vote to withdraw from

Plan to revert back to OpenZipkin

As you know, we voted to withdraw [1] from the Incubator back to the https://github.com/openzipkin/ org, which still exists and has active projects inside. Based on a previous inquiry to the Incubator [2], we expect no resistance to this. The same thread noted ODF Toolkit was the most recent to wi

Non Apache related discussions should move to our old google groups

The zipkin team are moving back to the OpenZipkin org per a recent vote [1]. This list will be reserved for Apache Incubator related topics, such as logistics of that move. For other concerns, please revert to our openzipkin mailing lists: general users: zipkin-u...@googlegroups.com https://group

[RESULT] [VOTE] Withdraw from the Apache Incubator

The Zipkin team conducted a 7 day vote to withdraw from the Apache Incubator back to its prior state in the OpenZipkin Github org. Below are the results which are unanimous +8. IPMC +1 Sheng Wu PPMC +7 Adrian Cole, Bas van Beek, José Carlos Chávez, Kristof Adriaenssens, Jorge Esteban Quilcate

Please review the downloads page ASAP

I'm getting really tired of a pile-on of complaints about lack of downloads page. Please review this https://github.com/apache/incubator-zipkin-website/pull/17 - To unsubscribe, e-mail: dev-unsubscr...@zipkin.apache.org For addit

Re: [ANNOUNCE] Apache Zipkin Dependencies (Incubating) version 2.2.0 Released

Thanks Craig. Up until now, we were under the impression that the website was an issue to sort before graduation, not before first release of a repo. As we have 9 repos to work on, we had deferred the site work until we got through the repos we had, rather than on each task. This was mainly a way

especially mentors: how do we get the note about issues link to go away?

Hi, team. We have 10 repositories each with an issues list in the default location in github. Clutch shows we are missing an issues list. Can someone please help make that note go away? http://incubator.apache.org/clutch/zipkin -A

FYI runbook of last release

Hi, all. Below is a runbook of what I used to release zipkin-dependencies 2.3.0, which is mostly following the stuff in the dubbo guide. We are getting close to a place where we can stamp out and/or possibly automate this (again), at least the non-human parts. Hope it helps, -A --- Run the prep

[VOTE] Release Apache Zipkin Dependencies (incubating) version 2.3.0

Hello Zipkin Community, This is a call for the vote to release Apache Zipkin Dependencies (incubating) version 2.3.0. The release candidates: https://dist.apache.org/repos/dist/dev/incubator/zipkin/zipkin-dependencies/2.3.0/ Git tag for the release: https://github.com/apache/incubator-zipkin-dep

Re: Attic the old scala source?

I think same rationale for the last brave release (way before apache) that included the archived code (version 3 types) https://github.com/apache/incubator-zipkin-brave/tree/4.13.x On Tue, Jun 4, 2019 at 12:46 PM Adrian Cole wrote: > > Hi, team. > > We have kept a branch of the ol

Attic the old scala source?

Hi, team. We have kept a branch of the old scala code in the main zipkin repo. However, with the old UI deleted, there's nothing in common anymore with that codebase. https://github.com/apache/incubator-zipkin/tree/scala I suggest we attic the scala branch to prevent someone from accidentally de

[VOTE] Release Apache Zipkin Brave (incubating) version 5.6.4

Hello Zipkin Community, This is a call for the vote to release Apache Zipkin Brave (incubating) version 5.6.4. The release candidates: https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave/5.6.4/ Git tag for the release: https://github.com/apache/incubator-zipkin-brave/tree/v5.6.4 Hash

Re: [Vote]New logo candidates

rm visible so that anyone can see the result briefly. > > Best Regards, > Seo-yeon. > > -Original Message- > From: "Adrian Cole" > To: ; > Cc: > Sent: 2019-06-03 (월) 17:26:06 (GMT+09:00) > Subject: Re: [Vote]New logo candidates > > thanks very m

Re: [Vote]New logo candidates

thanks very much, Seo Yeon. This is really helpful to not only have some logo choices, but also help moderating the selection! One thing is I think we want the logo choices to say just Zipkin or Apache Zipkin (not OpenZipkin) as this will help clarify the brand. I think when you first started hel

Re: Is the DEPENDENCIES file a requirement or a nice-to-have?

Thanks, Justin. Crystal clear! On Sun, Jun 2, 2019 at 3:58 PM Justin Mclean wrote: > > Hi, > > > Can someone clarify if packaging a file named DEPENDENCIES is required > > or a nice-to-have? > > It’s a nice to have. You’re releases do need to have no Category X licence > (e.g. GPL) dependancies.

Re: On constant feedback from various people that we've missed something

I fleshed out as much as I could in a few hours today. Hope it helps! Please edit as you see fit. https://cwiki.apache.org/confluence/display/ZIPKIN/Email+templates On Sat, May 18, 2019 at 6:27 PM Adrian Cole wrote: > > fyi I put the first template up as at least my release vote form

Re: [VOTE] Release Apache Zipkin Reporter (incubating) version 2.8.3

Thanks, Andriy. We have been working with the understanding that we get "mvn test" to execute as many projects include integration tests that have some workstation sensitivity, but are not required to execute for the project to pass tests (unit tests). For example, we have no plans to be a docker

Re: [VOTE] Release Apache Zipkin Reporter (incubating) version 2.8.3

+1 * Source archive has expected name * SHA512 checksum is correct * Provided GPG key is in KEYS file * GPG signature is valid, made with the provided key * Base dir in archive has expected name * Git tree at provided revision matches source archive * DISCLAIMER and NOTICE look good * LICENSE look

Re: [VOTE] Release Apache Zipkin Dependencies (incubating) version 2.2.0

+1 * Source archive has expected name * SHA512 checksum is correct * Provided GPG key is in KEYS file * GPG signature is valid, made with the provided key * Base dir in archive has expected name * Git tree at provided revision matches source archive * DISCLAIMER and NOTICE look good * LICENSE look

ignore: test email

credentials. name: Adrian Cole email address: adrianc...@apache.org treat as alias: check Reply-to address: dev@zipkin.apache.org - To unsubscribe, e-mail: dev-unsubscr...@zipkin.apache.org For additional commands, e-mail: dev-h

Re: On constant feedback from various people that we've missed something

fyi I put the first template up as at least my release vote formatting wasn't contested in multiple votes so far. https://cwiki.apache.org/confluence/display/ZIPKIN/Email+templates On Sat, May 11, 2019 at 3:42 AM Adrian Cole wrote: > > It seems that no one has a correct template as

Re: Can we please rally to get out of the incubator?

think release should not be a block. > > Sheng Wu > Apache Skywalking, ShardingSphere, Zipkin > > > > > 在 2019年5月16日，下午8:13，Adrian Cole 写道： > > > >> If we can cut the release once for this 10 repoes, we don't need to > >> go through the voting proce

Re: [VOTE] Release Apache Zipkin (incubating) version 2.14.0

/0571e9dd1b7711c588a38d8a664378ce7df31c72592edcbe8ab8a72b@%3Cgeneral.incubator.apache.org%3E On Thu, May 16, 2019 at 2:27 PM Adrian Cole wrote: > > Thanks for the fast voting! > > I'm attempting a parallel vote recommended here > https://lists.apache.org/thread.html/b4299fa86e9ad57479260a3574ce2f663f37

Fwd: Travel Assistance for ApacheCon NA Las Vegas 2019 now open.

For those interested in going to the 20th anniversary ApacheCon, but can't for financial reasons... please consider applying. -- Forwarded message - From: Gavin McDonald Date: Fri, May 17, 2019, 9:12 AM Subject: Travel Assistance for ApacheCon NA Las Vegas 2019 now open. To: Hi

Re: [VOTE] Release Apache Zipkin (incubating) version 2.14.0

; * Built the kit from source > * Checked the release tag and release note > * There is no binary in the source release kit > * License and Notice are OK > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, May 16, 2019 at 12:16 AM Adrian Cole wrote:

Re: Can we please rally to get out of the incubator?

> If we can cut the release once for this 10 repoes, we don't need to > go through the voting process one by one. > Is it possible? ironically, I noticed dubbo is graduating despite only releasing a few of their repos. Majority have no releases at all. I would like to attempt graduation after we'

Can we please rally to get out of the incubator?

This is addressed specifically to mentors. Can one or more of you please help us get out of the incubator. I think if we are honest, no one is going to want to release ten projects with the additional votes required from unrelated people. Currently, our votes don't matter and it is kindof frustrat

Re: next release will be zipkin again :)

closing this thread.. here's the release vote https://lists.apache.org/thread.html/03b215cc4a6e10a7092fe39b6ce87d3a964f35b6e181e12da4d45432@%3Cdev.zipkin.apache.org%3E On Wed, May 15, 2019 at 3:41 PM Adrian Cole wrote: > > Hi, folks. > > Before, we chatted about releasing the

Re: how do we address QuickStart and not asking users to do things laborious

closing this topic with https://github.com/apache/incubator-zipkin-website/issues/12 as far as I am concerned.. case closed here. thanks, ignasi On 2019/05/15 16:35:47, Adrian Cole wrote: > I see.. if this was about the website, I can imagine there is a lot to > do there. We haven'

Re: how do we address QuickStart and not asking users to do things laborious

referring to the > Zipkin website. Apologies for the misunderstanding. I'll follow up on > the issue. > > > > On Wed, 15 May 2019 at 18:06, Adrian Cole wrote: > > > > I added an issue for the mentors to figure out how to handle your > > feedback, Ig

[VOTE] Release Apache Zipkin (incubating) version 2.14.0

Hello Zipkin Community, This is a call for the vote to release Apache Zipkin (incubating) version 2.14.0. The release candidates: https://dist.apache.org/repos/dist/dev/incubator/zipkin/zipkin/2.14.0/ Git tag for the release: https://github.com/apache/incubator-zipkin/tree/v2.14.0 Hash for the

Re: how do we address QuickStart and not asking users to do things laborious

I added an issue for the mentors to figure out how to handle your feedback, Ignasi https://github.com/apache/incubator-zipkin/issues/2597 take care, -A On Wed, May 15, 2019 at 11:36 PM Adrian Cole wrote: > > Hi, Ignasi. > > There have been several mail threads about how voted s

Re: how do we address QuickStart and not asking users to do things laborious

he software, but the distinction should be clear. > > If that page exists (which is not the case now), I see no issue in > keeping the Quickstart page as-is, as long as we meet the previous > criteria and Quickstart is seen as "hey, to get the official release > you can go here

Re: GitHub PR -> Multi-branch Jenkins pipeline triggering

PS thanks all. I think we are good now as I've noticed pull requests getting magically checked now. -A On Sat, May 11, 2019 at 6:01 AM Allen Wittenauer wrote: > > > > > On May 10, 2019, at 2:04 PM, Zoltán Nagy wrote: > > > > In Zipkin (Incubating) we have a multi-branch pipeline building all ou

Re: [VOTE] Release Apache Zipkin (incubating) version 2.13.0

fixed all the things (but 1) mentioned, Ignasi. Some were very old README glitches (pre ASF). There's only one thing which I suspect not a blocker, but I did want to follow up on. forked a thread on that here https://lists.apache.org/thread.html/a7a9d52b91128a932329448a3fda62a077a6c94ccfec0e734e

how do we address QuickStart and not asking users to do things laborious

Hi, all. I went to cleanup things mentioned by Ignasi in his last review here: https://lists.apache.org/thread.html/fcc730ad01eb55293f7a174a3b5301f4a277b6222c7bb821d33faf2e@%3Cdev.zipkin.apache.org%3E What is troubling is this one: "Quickstart page should encourage using official releases instea

next release will be zipkin again :)

Hi, folks. Before, we chatted about releasing the reporter project next, but as Rag and I did some big perf work on the codec library, it is better to release zipkin again (so that reporter and dependencies jobs can use the faster codec). So, sometime shortly we'll start another Zipkin release. T

Re: On constant feedback from various people that we've missed something

t; HTH, > > I. > > [1] https://s.apache.org/jclouds212 > > > > On Sat, May 11, 2019, 03:43 Adrian Cole wrote: > > > It seems that no one has a correct template as regardless of who we > > copy, and regardless of if they have graduated or not, someone in the > &g

Re: Jenkins job cleanups

ncubator-zipkin/incubator-zipkin/branches/ On Fri, May 10, 2019 at 7:27 PM Zoltán Nagy wrote: > > Thank you for keeping our CI setup clean! > > On Fri, May 10, 2019 at 6:10 AM Adrian Cole wrote: > > > FYI I did this, leaving the magic ones > > https://builds.apache.o

On constant feedback from various people that we've missed something

It seems that no one has a correct template as regardless of who we copy, and regardless of if they have graduated or not, someone in the IPMC can find a problem in our email notifications. To reduce this friction, I've created a wiki where we can paste the last known good template. If you get advi

release manager volunteer for zipkin reporter?

Hi, team. Thanks to Rag for releasing Zipkin 2.13, we can now release the next patch of Zipkin reporter. I've checked the repo and think it is ok, but would be good to double-check https://github.com/apache/incubator-zipkin-reporter-java Any volunteer to release this? It would be best to start tha

Re: Jenkins job cleanups

FYI I did this, leaving the magic ones https://builds.apache.org/job/GH-incubator-zipkin/ Thanks, Zoltán for adding the magic! -A On Wed, May 8, 2019 at 9:28 PM Adrian Cole wrote: > > Hi, team. > > I think a lot of us were unaware (despite being told) that there is > magic to ma

Re: [VOTE] Release Apache Zipkin (incubating) version 2.13.0

Thanks for the close review and all the notes, Ignasi. We have some kinks in the Apache website publishing but they should be fixed shortly (then all the links changed). Expect all notes addressed before our follow up release of 2.14. cheers! -Adrian On Thu, May 9, 2019, 4:49 PM Ignasi Barrera

Messaging instrumentation abstraction design

Hi, folks. Jorge has taken on the long overdue messaging instrumentation abstraction. I've started a wiki page, which is something we can all contribute to. If you are interested in updates, please follow the page below https://cwiki.apache.org/confluence/display/ZIPKIN/Messaging+instrumentation+a

Jenkins job cleanups

Hi, team. I think a lot of us were unaware (despite being told) that there is magic to make Jenkins jobs for each project. This means we have some duplication between the generated and the explicitly created. Unless someone screams, I will be deleting the jobs that were explicitly created. Ex. ma

Re: Delete Kafka 0.8 support

ávez > > > tir. 7. mai 2019 kl. 16:03 skrev Brian Devins-Suresh : > > > +1 based on Jorge's response. My inclination is to follow what the major > > vendors for each component are supporting with a bit of lag possibly. > > > > On Tue, May 7, 2019 at 4:36 AM Ad

Re: Delete Kafka 0.8 support

https://github.com/apache/incubator-zipkin/pull/2564 removes this and the PR description includes text I plan to weave into the release notes. On 2019/05/07 00:48:52, Adrian Cole wrote: > Hi, team. > > We are readying release announcement for Zipkin 2.13 (it is pending > IPMC vo

Delete Kafka 0.8 support

Hi, team. We are readying release announcement for Zipkin 2.13 (it is pending IPMC vote still). I think we should say this is the last version we publish Kafka 0.8 support. I can't find any support matrix from Kafka, but it is very old, almost 4 years old since last release of Kafka 0.8. Removing

Re: Is it time to stop supporting Cassandra <3.11.3?

uld just follow the same general principle. If maintained > upstream, we have to keep it (run CI etc), if not, it's best effort but not > ensured. > > On Mon, May 6, 2019 at 4:18 AM Adrian Cole wrote: > > > Hi, team. > > > > You may recall that we are maintaining d

Is it time to stop supporting Cassandra <3.11.3?

Hi, team. You may recall that we are maintaining double code for cassandra and have been for years. This is due to the minimum requirement of our "cassandra3" storage (3.11.3). Initially the gate was around those using Datastax, but I am not sure if this problem is valid anymore or not, as there a

Re: Elasticsearch and versions

orts. We advise users to be current with Elastic's supported version policy, to avoid being unable to upgrade Zipkin. https://github.com/apache/incubator-zipkin/releases/tag/v2.13.0 On 2019/04/27 00:03:17, Adrian Cole wrote: > > What's the best way of communicating timelines

Re: [VOTE] Release Apache Zipkin (incubating) version 2.13.0

Thanks, Raja for doing the release. I know you are in-between houses, so pretty awesome that you've made time for this. +1 Besides the usual verifications, I also ran "mvn test" from an unzip and it passed. I also built and ran the server from the source dist using instructions at the bottom of t

Re: on the IDL distribution (zipkin-api) and our source verification tooling

> > IMHO that means prioritizing voting over tool polish. > > I guess that's aimed at me? :D Sorry for missing the new vote thread. I'll > go and do the thing now. it was more about my guess that the scary output on zipkin-api (lack of polish) was behind why folks voted on layout (no scary output)

Re: on the IDL distribution (zipkin-api) and our source verification tooling

> Everyone who is on the IPMC can vote, if you have a couple > minutes, please help vote this one. > > https://lists.apache.org/thread.html/0d121cede77529c339e181036b79fde8a52e7809eea1322aa6e8f3fb@%3Cdev.zipkin.apache.org%3E Typo, I meant everyone on the PPMC (though also IPMC can vote of course)

on the IDL distribution (zipkin-api) and our source verification tooling

Hi, team. I'm concerned about lack of participation on the zipkin-api vote. I'm concerned it might be because people expect a one-line command to work flawlessly, and they saw the scary output I pasted, and aren't interested in trying. The scary output is about things that are not required for AS

Re: [VOTE] Release Apache Zipkin Layout Factory (incubating) version 0.0.5

y the time we go IPMC vote. Best, -a On Mon, Apr 29, 2019 at 5:24 PM Adrian Cole wrote: > > weird that should have made Jenkins fail.. rat itself is not critical unless > it stops the build from working. rat is just another faulty tool we use > > On Mon, Apr 29, 2019, 4:39 PM Sheng

Re: [VOTE] Release Apache Zipkin Layout Factory (incubating) version 0.0.5

id, made with the provided key > > [PASS] Base dir in archive has expected name > > [PASS] Git tree at provided revision matches source archive > > [PASS] No .gitignore-d files in source archive > > [PASS] DISCLAIMER and NOTICE look good > > [PASS] LICENSE looks good >

is appveyor ok in ASF?

Hi, team. I recall there's a very limited supply of windows slaves in ASF Jenkins, and concerned if we turn CI on with one, we'll prevent other smaller projects who need them more. I wonder if appveyor is an approved tech in ASF? If so, I could add a small job to verify our build works with Windo

Re: [VOTE] Release Apache Zipkin API (incubating) version 0.2.1

+1 Note: our work-in-progress source verification tool isn't designed yet for projects that have very different contents in the source dist from the github repository. This is currently not a priority as neither do we frequently update our IDL, but also it would be hard to special case this. Her

Re: Who wants to make Zipkin server's first release in Apache?

(HEAD -> master, origin/master, origin/HEAD) Author: Adrian Cole Date: Sun Apr 28 08:05:51 2019 +0800 Extracts zipkin-tests jar before we publish to o.a.z.zipkin2 namespace (#2546) This fixes an anti-pattern before we commit to it in the new namespace.

Who wants to make Zipkin server's first release in Apache?

Hi, team. I'd like to offer the honors to whoever wants to pull the trigger on zipkin 2.13.0 release. I hope that I've cleared the path, but I think it is important for us all to give a try at releasing once. This involves cutting the release and sending the vote notification. Following dubbo's t

Re: [master] master is SUCCESS (#2)

yay On Sat, Apr 27, 2019, 5:56 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

tracking issue for graduation

Hi, team. I just made a tracking issue for things not blocking for incubating releases, but must be addressed prior to graduation. Lacking a better place, and knowing some things do not affect github repos, I made a checkbox thing on the main zipkin repo. https://github.com/apache/incubator-zipki

Re: [GitHub] [incubator-zipkin-website] jcchavezs commented on issue #5: fix: reenables the zipkin-api filter.

since zipkin-api is updated infrequently some automation could help. it doesnt necessarily need to use a bot as things like triggering downstream stuff can also be done in Jenkins flows and I dont know why we would want to not update our website if we updated our api (dependabot and friends are eff

Re: Elasticsearch and versions

> What's the best way of communicating timelines of support? I think we can use the following, but most important is the release notes * release notes * clarification in the README * note in LastMonthInZipkin * tweet * email the the not quite defunct old user mailing list sg? ---

Re: [VOTE] Release Apache Zipkin API (incubating) version 0.2.1

f ourselves, let's see if this is even a problem at all. > > On Fri, Apr 26, 2019 at 1:04 AM Adrian Cole wrote: > > > spamming, but there's a lot of context with IDL.. people still > > copy/pasta our IDL files. One good thing about having finally a source > > distri

Re: Elasticsearch and versions

On Fri, Apr 26, 2019 at 11:21 AM Jordi Polo Carres wrote: > > 2.x was eol one year ago. I think it is fair to drop it. > > 5.x was eol 1 month ago. Maybe give it 6 more months? > > ES deprecate versions every year or so. Fast for many enterprise > environment Sounds OK, but we haven't given any

Re: [VOTE] Release Apache Zipkin Layout Factory (incubating) version 0.0.5

+1 verified the following [PASS] Source archive has expected name [PASS] SHA512 checksum is correct [PASS] Provided GPG key is in KEYS file [PASS] GPG signature is valid, made with the provided key [PASS] Base dir in archive has expected name [PASS] Git tree at provided revision matches source arc

Re: [VOTE] Release Apache Zipkin API (incubating) version 0.2.1

ged binary projects, this particular repo stands alone as source. We've never had a complete source dist here before! On Fri, Apr 26, 2019 at 9:01 AM Adrian Cole wrote: > > PS it was my call to make a custom assembly for this repo. What > happened before was that you could barely

Re: [VOTE] Release Apache Zipkin API (incubating) version 0.2.1

d possibly another user would as well. On Fri, Apr 26, 2019 at 8:48 AM Adrian Cole wrote: > > Hi, Zoltan. > > The api is an IDL project only, there is nothing to build. The actual > source here is all protos, swagger and thrift IDLs. > > What's probably distracting is tha

Re: [VOTE] Release Apache Zipkin Layout Factory (incubating) version 0.0.5

Thanks for checking, Zoltan. I will comment on your question below. > Note: the artifact naming here was a bit confusing for me. We have one > extra "zipkin-" here compared to previously migrated projects. Compare the > URL paths with brave-karaf: > * > https://dist.apache.org/repos/dist/release/i

Re: [VOTE] Release Apache Zipkin API (incubating) version 0.2.1

Hi, Zoltan. The api is an IDL project only, there is nothing to build. The actual source here is all protos, swagger and thrift IDLs. What's probably distracting is that we currently have a partial source distribution in maven to depend on the protos (though we only use them in tests). If you ign

on untangling inter-repo dependencies

Hi, team. You may be aware that we are migrating 4 repos which have some interdependence. I wanted to bring forward this concern so that it can be squashed :) While there are inter-dependencies, there's no reason why our first release should (or even can) resolve all dependencies to org.apache.zi

Re: Next up: ASF incubating source releases!

wrote: > > > I should be able to take on b3-propagation. Though the dynamo PR is what I > > will be focused on as soon as the next Zipkin release is out > > > > -Brian > > > > On Tue, Apr 16, 2019 at 4:58 AM Adrian Cole > > wrote: > >

Re: Elasticsearch and versions

thanks for the feedback, Jordi. I think one point you mention is a bit of whistling past the graveyard though. > People can stay in older Zipkin versions till they migrate. > Is not like we > break their current installation. many people historically, even you personally, have asked for extremely

Fwd: [Yelp/py_zipkin] Better documentation - generate readthedocs compatible docs (#127)

forwarding this as good doc efforts should be shared! -- Forwarded message - From: Daniele Date: Tue, Apr 23, 2019, 4:22 AM Subject: [Yelp/py_zipkin] Better documentation - generate readthedocs compatible docs (#127) To: Yelp/py_zipkin Cc: Subscribed @jstrfd

Re: Elasticsearch and versions

To put things in perspective about the upgrade concern and libraries. It is very often the case that when using elastic's hadoop library, supporting most recent Elasticsearch requires immediate upgrade. This means a release of the job. That part is not so much the problem expect in the issue menti

Re: [GitHub] [incubator-zipkin-website] abesto commented on issue #2: Sync changes from openzipkin/openzipkin.github.io

be nice to keep the repo "clean" and > populate zipkin-api "properly". I don't have a strong opinion on this > trade-off, happy to leave it to JC and you (and whoever else might actually > have an opinion). > > On Mon, Apr 22, 2019 at 9:37 AM Adrian Cole > wr

Re: [GitHub] [incubator-zipkin-website] abesto commented on issue #2: Sync changes from openzipkin/openzipkin.github.io

This is great news, Zoltan. Thanks for all the help. I've noticed the website looks current now (except the missing link to zipkin-api but that's on the burner) On Mon, Apr 22, 2019 at 5:08 PM GitBox wrote: > > abesto commented on issue #2: Sync changes from > openzipkin/openzipkin.github.io >

Elasticsearch and versions

Hi, team. There have been some interesting turns in Elasticsearch, and some things that have always been around. TL;DR; we are being forced into a corner where we have to immediately inherit Elastic the company's version policy, and we need to figure out what to do about that. ## Licensed feature

can someone help restore functionality of our website

Hi, team. you know we have zipkin.io but the first effort was to get http://zipkin.apache.org/ setup. We have a couple problems 1. there is drift as people make changes to https://github.com/openzipkin/openzipkin.github.io instead of https://github.com/apache/incubator-zipkin-website 2. people don

maven package name for main repo

I updated a github issue about the package name for the main zipkin assets in maven. I'm pinging here as we no longer have an @core shortcut in github to notify the devs. While this mainly affects java, it does have some impact on download urls Please have a look and comment https://github.com/apa

note our github org lists don't work anymore

I think some have been used to pinging experts on github using shortcuts like @openzipkin/elasticsearch https://github.com/apache/incubator-zipkin/issues/2403 Now that our repo is in the apache org, we can't do this anymore as those links are dead. If anyone knows an alternative, it would be handy

Re: Next up: ASF incubating source releases!

> I volunteer for "zipkin-layout-factory" and "zipkin-api" if they are still > available. surprise surprise.. they are! :D - To unsubscribe, e-mail: dev-unsubscr...@zipkin.apache.org For additional commands, e-mail: dev-h...@zipk

Next up: ASF incubating source releases!

Hi, team. You may have noticed that INFRA have moved the following repos zipkin-layout-factory zipkin-api b3-propagation zipkin (zipkin-reporter-java had an access glitch on our end, should be done soon) This means the next release will be apache from each of these. I offer to handle the main z

new committer: Anuraag Agrawal

The Project Management Committee (PPMC) for Apache Incubating Zipkin has invited Anuraag Agrawal to become a committer and we are pleased to announce that he has accepted. For nearly 3 years, Anuraag Agrawal (goes by Rag and is anuraaga on github) has been doing good work in Zipkin. He wrote our f

feedback needed on pull request about remote service name

Hi, all. This is referencing a non-ASF repo, but that's by accident. We've had a request to move it for a week [1] and I can't sensibly block technical discussions longer just because of jurisdiction. I'll proceed to the point now :) We have a long term issue with local and remote services being s

Last month in Zipkin March is out

read all about it.. then click follow on our wiki to avoid manual span (because automatic spam is better :)) https://cwiki.apache.org/confluence/display/ZIPKIN/LastMonthInZipkin See you, -A - To unsubscribe, e-mail: dev-unsubscr

Re: Breaking change in release verifier script

works for me! thanks for the heads up On Thu, Apr 4, 2019 at 5:04 PM Zoltán Nagy wrote: > > If you're not using > https://github.com/openzipkin-contrib/apache-release-verification/, feel > free to ignore this. > > I've just clicked merge on > https://github.com/openzipkin-contrib/apache-release-v

Re: Anyone for the March Incubator report?

n Tue, Apr 2, 2019, 7:18 AM Brian Devins-Suresh > wrote: > > > I'm honestly not sure where our report goes during the months where we > are > > not reporting to the board > > > > On Tue, Apr 2, 2019 at 5:04 AM Adrian Cole > > wrote: > > > >

  1   2   3   >