Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+2/-4/💬7)
  2 issues created:
  - How multiple APMs in a process can "collaborate" on a given trace-context? (by yurishkuro)
    https://github.com/w3c/trace-context/issues/335 
  - Trace-Context W3C Candidate Recommendation 24 September 2019 Review Notes (by bobstrecansky)
    https://github.com/w3c/trace-context/issues/334 

  3 issues received 7 new comments:
  - #335 How multiple APMs in a process can "collaborate" on a given trace-context? (1 by untitaker)
    https://github.com/w3c/trace-context/issues/335 
  - #289 Clarify handling of multiple tracestate headers (2 by arminru, mwear)
    https://github.com/w3c/trace-context/issues/289 
  - #58 Provide vendor/open source product name register for tracestate (4 by AloisReitbauer, danielkhan, yurishkuro)
    https://github.com/w3c/trace-context/issues/58 

  4 issues closed:
  - Clarify handling of multiple tracestate headers https://github.com/w3c/trace-context/issues/289 
  - Provide vendor/open source product name register for tracestate https://github.com/w3c/trace-context/issues/58 
  - Update tracestate test to validate new tenant format https://github.com/w3c/trace-context/issues/331 [needs tests] 
  - Add negative test cases for Tracestate value https://github.com/w3c/trace-context/issues/304 [needs tests] 



Pull requests
-------------
* w3c/trace-context (+0/-2/💬0)
  2 pull requests merged:
  - Update test cases to reflect the latest spec change
    https://github.com/w3c/trace-context/pull/332 
  - Add implementation page
    https://github.com/w3c/trace-context/pull/333 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg