Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+0/-1/💬0)
  1 issues closed:
  - Randomness flag bit https://github.com/w3c/trace-context/issues/467 

* w3c/correlation-context (+0/-3/💬2)
  2 issues received 2 new comments:
  - #84 Different behaviour in private browsing/incognito mode? (1 by kalyanaj)
    https://github.com/w3c/baggage/issues/84 
  - #83 Name 'baggage' is a metaphor and could be hard for non-native English speakers (1 by kalyanaj)
    https://github.com/w3c/baggage/issues/83 

  3 issues closed:
  - Different behaviour in private browsing/incognito mode? https://github.com/w3c/baggage/issues/84 
  - Name 'baggage' is a metaphor and could be hard for non-native English speakers https://github.com/w3c/baggage/issues/83 
  - Consider lowering baggage limits https://github.com/w3c/baggage/issues/65 



Pull requests
-------------
* w3c/trace-context (+0/-1/💬0)
  1 pull requests merged:
  - Add the random trace id flag
    https://github.com/w3c/trace-context/pull/474 

* w3c/correlation-context (+0/-3/💬3)
  2 pull requests received 3 new comments:
  - #89 Define lower bounds for header limits (2 by SergeyKanzhelev, dyladan)
    https://github.com/w3c/baggage/pull/89 
  - #88 Use a more descriptive sentence instead of "opaque" (1 by SergeyKanzhelev)
    https://github.com/w3c/baggage/pull/88 

  3 pull requests merged:
  - Use a more descriptive sentence instead of "opaque"
    https://github.com/w3c/baggage/pull/88 
  - Define lower bounds for header limits
    https://github.com/w3c/baggage/pull/89 
  - Remove unenforceable requirement to strip whitespace
    https://github.com/w3c/baggage/pull/87 


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config