W3C home > Mailing lists > Public > public-trace-context@w3.org > April 2019

Weekly github digest (Distributed Tracing WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 02 Apr 2019 17:00:59 +0000
To: public-trace-context@w3.org
Message-Id: <E1hBMmR-0006Yq-6W@uranus.w3.org>



Issues
------
* w3c/trace-context (+0/-2/💬7)
  4 issues received 7 new comments:
  - #268 Add more editors for the document and add credits section (4 by SergeyKanzhelev, plehegar, nikmd23)
    https://github.com/w3c/trace-context/issues/268 [editorial] 
  - #194 Trace-id and Span-id - What makes up valid bytes? (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/194 [discuss-next-meeting] [editorial] 
  - #264 Please clarify tracestate purpose (1 by falenn)
    https://github.com/w3c/trace-context/issues/264 [question] 
  - #239 Header limits are obsolete and should be removed (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/issues/239 [discuss-next-meeting] [enhancement] 

  2 issues closed:
  - Trace-id and Span-id - What makes up valid bytes? https://github.com/w3c/trace-context/issues/194 [discuss-next-meeting] [editorial] 
  - How and when are you allowed to restart a trace https://github.com/w3c/trace-context/issues/146 [discuss-next-meeting] 



Pull requests
-------------
* w3c/trace-context (+1/-6/💬4)
  1 pull requests submitted:
  - [WIP] Add processing model to spec (by AloisReitbauer)
    https://github.com/w3c/trace-context/pull/270 

  3 pull requests received 4 new comments:
  - #248 Make tracestate limit the responsibility of a platform (2 by SergeyKanzhelev, plehegar)
    https://github.com/w3c/trace-context/pull/248 [discuss-next-meeting] [substantial] 
  - #257 describe what invalid means (1 by plehegar)
    https://github.com/w3c/trace-context/pull/257 [editorial] 
  - #258 added potential privacy risk (1 by plehegar)
    https://github.com/w3c/trace-context/pull/258 [privacy] 

  6 pull requests merged:
  - prepare for CR
    https://github.com/w3c/trace-context/pull/267 
  - traceparent restart should require tracestate cleanup rationale
    https://github.com/w3c/trace-context/pull/260 [editorial] 
  - added potential privacy risk
    https://github.com/w3c/trace-context/pull/258 [privacy] 
  - describe what invalid means
    https://github.com/w3c/trace-context/pull/257 [editorial] 
  - Make tracestate limit the responsibility of a platform
    https://github.com/w3c/trace-context/pull/248 [discuss-next-meeting] [substantial] 
  - Changes to wording, structure, grammar and spelling
    https://github.com/w3c/trace-context/pull/259 [discuss-next-meeting] 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg
Received on Tuesday, 2 April 2019 17:01:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:36:42 UTC