Issues
------
* ietf-tapswg/api-drafts (+0/-3/💬6)
 4 issues received 6 new comments:
 - #145 Draft should point at implementations somewhere (2 by mwelzl, theri)
https://github.com/ietf-tapswg/api-drafts/issues/145 [Implementation] [ready for text] - #356 Fix "Implementing maintenance" section (2 by mwelzl, tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/356 [Implementation] [help wanted] - #248 Implementation should separate out protocol-specific bits (1 by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/248 [Implementation] - #309 Clarification on queued receives (1 by MaxF12) https://github.com/ietf-tapswg/api-drafts/issues/309 [API]
 3 issues closed:
- API Draft author editorial comments https://github.com/ietf-tapswg/api-drafts/issues/313 [API] [ready for text] - Implementation should separate out protocol-specific bits https://github.com/ietf-tapswg/api-drafts/issues/248 [Implementation] - Fix "Implementing maintenance" section https://github.com/ietf-tapswg/api-drafts/issues/356 [Implementation] [help wanted]


Pull requests
-------------
* ietf-tapswg/api-drafts (+1/-1/💬0)
 1 pull requests submitted:
 - Introduce pooled connections as optional implementation detail (by philsbln)
https://github.com/ietf-tapswg/api-drafts/pull/358
 1 pull requests merged:
 - Fixes #313 per Gorry's comments
https://github.com/ietf-tapswg/api-drafts/pull/346

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps

Reply via email to