- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 22 Jan 2019 17:01:11 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1glzQF-00076o-R1@uranus.w3.org>
Issues ------ * w3c/trace-context (+1/-8/💬17) 1 issues created: - Change wording of trace context propagation definition. (by danielkhan) https://github.com/w3c/trace-context/issues/244 9 issues received 17 new comments: - #228 Enable Rewrap or similar solution to limit the line width and simplify reviews (5 by AloisReitbauer, danielkhan, yurishkuro) https://github.com/w3c/trace-context/issues/228 [editorial] - #235 Decide, if we have to suggest an intrinsic format of trace-id (3 by AloisReitbauer, danielkhan, yurishkuro) https://github.com/w3c/trace-context/issues/235 [discuss-next-meeting] [editorial] - #233 Decide, if 'generic tracer' should be mentioned in intro example (2 by AloisReitbauer, danielkhan) https://github.com/w3c/trace-context/issues/233 [discuss-next-meeting] [editorial] - #238 Decide, if we should explain OWS though we refer to the spec where it's defined (2 by AloisReitbauer) https://github.com/w3c/trace-context/issues/238 [discuss-next-meeting] [editorial] - #234 Decide, if reuse of last trace ID in traceparent needs to be mentioned in spec (1 by AloisReitbauer) https://github.com/w3c/trace-context/issues/234 [editorial] [trace-context] - #236 Decide, if we want to mention span ID (1 by danielkhan) https://github.com/w3c/trace-context/issues/236 [discuss-next-meeting] [editorial] - #237 Section on Recorded flag should be shorter and more precise (1 by AloisReitbauer) https://github.com/w3c/trace-context/issues/237 [discuss-next-meeting] [editorial] - #239 Header limits are obsolete and should be removed (1 by AloisReitbauer) https://github.com/w3c/trace-context/issues/239 [trace-context] - #240 Move mutations into processing model (1 by danielkhan) https://github.com/w3c/trace-context/issues/240 [discuss-next-meeting] [editorial] 8 issues closed: - Decide, if we have to suggest an intrinsic format of trace-id https://github.com/w3c/trace-context/issues/235 [editorial] - Change wording of trace context propagation definition. https://github.com/w3c/trace-context/issues/244 - Decide, if reuse of last trace ID in traceparent needs to be mentioned in spec https://github.com/w3c/trace-context/issues/234 [editorial] - Decide, if 'generic tracer' should be mentioned in intro example https://github.com/w3c/trace-context/issues/233 [editorial] - Decide, if we want to mention span ID https://github.com/w3c/trace-context/issues/236 [editorial] - Move mutations into processing model https://github.com/w3c/trace-context/issues/240 [editorial] - Decide, if we should explain OWS though we refer to the spec where it's defined https://github.com/w3c/trace-context/issues/238 [editorial] - HEXDIG has uppercase [A-F] https://github.com/w3c/trace-context/issues/219 Pull requests ------------- * w3c/trace-context (+1/-5/💬7) 1 pull requests submitted: - Echidna (by plehegar) https://github.com/w3c/trace-context/pull/243 4 pull requests received 7 new comments: - #229 use the lower case HEXDIGLC rule in abnf definition (3 by SergeyKanzhelev, AloisReitbauer) https://github.com/w3c/trace-context/pull/229 [ready for review] - #221 [WIP] Changed abstract to define the problem we are solving and the proposed solution (2 by SergeyKanzhelev) https://github.com/w3c/trace-context/pull/221 - #224 - Fixes minor spelling- and grammar mistakes (1 by danielkhan) https://github.com/w3c/trace-context/pull/224 [discuss-next-meeting] [editorial] [ready for review] - #242 [WIP] Editorial changes to HTTP Header Format (1 by danielkhan) https://github.com/w3c/trace-context/pull/242 5 pull requests merged: - [WIP] Editorial changes to HTTP Header Format https://github.com/w3c/trace-context/pull/242 - - Fixes minor spelling- and grammar mistakes https://github.com/w3c/trace-context/pull/224 [editorial] [ready for review] - use the lower case HEXDIGLC rule in abnf definition https://github.com/w3c/trace-context/pull/229 [ready for review] - Fix file case https://github.com/w3c/trace-context/pull/226 [editorial] [ready for review] - Fix link https://github.com/w3c/trace-context/pull/230 [editorial] [ready for review] * w3c/distributed-tracing-wg (+1/-1/💬1) 1 pull requests submitted: - Added minutes for 2019-01-15 (by danielkhan) https://github.com/w3c/distributed-tracing-wg/pull/8 1 pull requests received 1 new comments: - #6 Add more goverance wording to the contribution.md (1 by SergeyKanzhelev) https://github.com/w3c/distributed-tracing-wg/pull/6 [w3c] 1 pull requests merged: - Added minutes for 2019-01-15 https://github.com/w3c/distributed-tracing-wg/pull/8 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, 22 January 2019 17:01:14 UTC