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
+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 Adrian Cole wrote:
> https://github.com/apache/incubator-zipkin/pull/2564 removes this and the
> PR description includes t
s we cannot do that: ASF
> > doesn't serve custom domains unless in very special circumstances (see
> > https://issues.apache.org/jira/browse/INFRA-16996) for more on this.
> We'll
> > need to update everything to zipkin.apache.org, and set up a redirect a
We should probably also CNAME zipkin.io to zipkin.apache.org, which might
solve the user problems too.
On Sun, Apr 21, 2019 at 1:53 AM José Carlos Chávez
wrote:
> I volunteer for this. But can't not start it until Tuesday (I am on
> holidays). If someone else feels like fixing it just go ahead,
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:
> > I volunteer for "zipkin-layout-factory" and "zipkin-api" if they are
> still
> > available.
>
> s
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:
> I will be doing the LastMonthInZipkin shortly
>
> https://wiki.apache.org/incubator/April2019 needs an entry for zipkin.
> Any volunteers?
>
>
Adrian reminded me that this thread existed.
I'll offer my 2 cents here, I think that the storage/reporter
implementations
that send to the vendor backends do not belong in the same repos as the
Zipkin and Zipkin library extensions that enable Zipkin use within cloud
environments. The distinction
+1 binding
Checked:
- 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 is named {module}-{version}
- Git tree at provided revision matches source archive
- No .gitignore-d fil
+1 binding
I checked:
- sha512 of zip
- gpg signature matches Adrian's key and is in key file
- git tag matches commit hash (git show v0.1.2)
- Source package contents match git tree (exceptions: .gitignore, NOTICE,
DEPENDENCIES, maven-wrapper stuff)
- LICENSE is Apache 2.0
- DISCLAIMER mentions i
Unfortunately I have to vote -1 on this
The maven-wrapper.jar file is still included in this release zip.
> Running check: no binary files
>> Executing `diff <(echo -n) <(find
/var/folders/3s/y4tnvxcn27lgt1t75g3cl2bmgp/T/tmpj0wq4iyy/unzipped/brave-karaf-0.1.2
-type f | xargs file | grep -v te
Alright, I moved the repo into contrib:
https://github.com/openzipkin-contrib/apache-release-verification
On Sat, Feb 16, 2019 at 7:20 AM Zoltán Nagy wrote:
> I propose we run the thing in Docker, so we have easy control of the
> environment. I don't expect problems here. Same goes for Java. We'
Hi Zoltan, to be honest I ended up doing the checks by hand on my work
computer so will have to recreate them.
I do however have a repo with the start of my dockerfile [1]. I added a
note about the approach I had planned on
taking in a comment. Please feel free to send me a PR, I could even
transfe
I actually started writing this myself too, I am creating a docker
container that
can run through the whole set of easy checks: GPG, sha512, repo/zip diff,
maven build, so I won't have to do these by hand in the future. I think
other
checks really should be done by hand, but I'm not opposed to a sc
+1 binding
I checked:
- sha512 of zip
- Source package compiles and tests (mvn test && mvn package)
- git tag matches commit hash (git show v0.1.2)
- Source package contents match git tree (exceptions: .gitignore, NOTICE,
DEPENDENCIES)
- LICENSE is Apache 2.0
- DISCLAIMER mentions incubation
- Sou
+1 as well
On Sun, Feb 10, 2019 at 4:23 AM Zoltán Nagy wrote:
> +1 for commits@ with replyTo dev@ - that's also how our Jenkins
> notifications are currently set up.
>
>
> On Sun, Feb 10, 2019 at 4:23 AM Adrian Cole
> wrote:
>
> > > Lots of projects send these to commits@ with the replyTo set t
+1
Are release votes not supposed to include some synopsis of the changes? I
know this is a first release within the incubator but it might be good to
just call that out?
On Sat, Feb 9, 2019 at 6:41 AM José Carlos Chávez
wrote:
> +1
>
> Den lør. 9. feb. 2019, 11:36 skrev Adrian Cole
> > > I ca
I think yeah, probably belongs on the dev list. I've added it in my reply.
As far as Jenkins goes. I think leaving things on Travis/Circle for now
should be our plan, but I do think we will want to move to Jenkins in
the future based on the fragility we have seen with Travis/Circle (the
reason we
Oh course I didn't have it starred.. whoops
On Sat, Dec 8, 2018 at 8:17 PM Adrian Cole wrote:
> I noticed recently that even some long term contributors didn't
> realize they never starred our main repo. If you want to, just forgot
> to, please click the star button!
>
> https://github.com/openz
Hi All,
I'm Brian Devins-Suresh, I (currently, stay tuned) work at Dealer.com/Cox
Automotive in Burlington Vermont in the
US. I got involved with Zipkin and Brave in late 2015. My team at the time
was building developer tooling and
owning some of the core applications. We built out our tr
Assuming we have access to the real time collaboration features of
Confluence
then that sounds like an easy win to me, and being part of the apache
domain means
that folks like Wu Sheng can access it. Sounds like a no brainer other than
the
imposed learning curve of yet another new tool
On Tue, Se
Hey Zoltan,
I'm willing to help you strategize here, I think largely what we have won't
need to change much. But see value from the formal release standpoint
of making our process more Apache-esch. Please feel free to email me
directly or start a doc of some kind (Google docs aren't available in
C
Just sent out my ICLA, already joined all the lists.
Thanks for the prodding Mick
On Mon, Sep 10, 2018 at 6:50 PM Mick Semb Wever wrote:
>
> > I think there might be some confusion about the email address. I've
> signed
> > and submitted the ICLA and subscribed to the mailing lists under "
> >
Hi All,
Can someone with Wiki edit access update my name from Brian Devins to Brian
Devins-Suresh?
Thanks,
Brian
23 matches
Mail list logo
