A little bit of optimization that reduces interestOps() calls
Self-referential type parameter fix
Fix covariant return types in ChannelConfig interfaces for method chaining

- Does it really worth doing this? I'm tempted to remove support for method chaining for ChannelConfig.
Don'T call ChannelPipeline.fireExceptionCaught(..) for outbound events
Support method chaining in ChannelFlushPromiseNotifier
Tighten up visibility
Tighten up visibility
Tighten up visibility
Let ChannelPromiseAggregator take a vararg of ChannelPromises and rename method
Clean up
Fix inspector warnings
Make CompositeyteBuf and MessageBuf call release() on its elements when it is deallocated
Make Channel*Invoker package private
Allow for method chaining
Prettify APIviz diagrams / Remove an empty package
Hide SnappyChecksumUtil
Tighten visibility
Fixing generic <> in documentation to display properly
Prettify APIviz / Tighten visibility / Move subclasses to top level / Remove unused UnknownSocksMessage
Add TODO