Dear SwiftNIO users,
Internally (so far, need to solve some issue before getting it public) we manage a source compatibility suite for SwiftNIO. Also, in case there are any security issues we may also want to give our users ahead-of-time notice.
I'm pleased to say we have now reached the point where we lost track what projects use SwiftNIO and who are the maintainers 
.
To not just favour the ones that came early we would like to give everybody the chance to post their project as SwiftNIO user and we will try to add it to our source compatibility suite and may give ahead-of-time notice in case of a security issue in SwiftNIO (don't worry there's isn't anything that we know about now, just in case).
If you don't want to share this publicly, a PM, email or any other way works too.
2 Likes
jonas_vapor
(Jonas Schwartz)
5
4 Likes
Thanks! Should we use test the master/5.0 branch there?
Yes, sorry for not mentioning this. That's the branch that is currently actively developed and is ready for a 5.0 final were it not that we defined 5.0 as having a few more features.
Thanks, added MongoKitten with the master/5.0 branch now. The tests didn't compile so for now it's without tests, let me know when the tests should compile again.
Yeah, we've got a lot of code locally still 
and we're working on the major 5 release sunday. Thank you 
2 Likes
