On Tue, Dec 13, 2011 at 5:57 PM, Christian Schwarz <[email protected]> wrote: > +1 for all points.. > > ...and some comments and additions: > > Javadoc and Unit tests : >> Same here : lots to do, but definitively mandatory. The Javadoc in MINA 3 >> is not bad, but need some cleanup. Unit tests, that's clearly an area we >> should spend some time. >> > Talking about test what about codecoverage ? If u use eclipse as IDE > http://www.eclemma.org/ can assist here! > > > Community support: > Actually we have the mailing lists and jira to communicate in all > directions. It both works well, but i think the user communication can be > improved. The mailing list doesn't provider any styling of the text, so > codesnippets are hard to read. Stackoverflow can help here, there is > actually a tag for MINA with some questions-> > http://stackoverflow.com/search?q=apache-mina . The MINA development team > could register a RSS-Feed for this tag to provide support. There is a huge > acceptance in the community for stackoverflow ! > > Greetings > Christian
Hi, About coverage, it's tested with the jenkins build (see the little graph at the bottom right) : https://builds.apache.org/view/M-R/view/MINA/job/MINA-trunk-jdk1.6-ubuntu/ About stack overflow, I'm already register on this tag, but I'm quite lazy :) Julien
