Hi folks, As some of you already know, I proposed somewhat radical changes in our current core API of MINA 2. At the first time, I though all the changes I proposed can be made before we release MINA 2 GA. However, after a couple of long IRC conversations and e-mail discussions, I realized it's not something that can happen within a few months. It's rather what we need to approach very carefully, as Emmanuel pointed out.
Moreover, we already released MINA 2.0.0-M1 and recommended our users to use it saying its core API is not likely to change and transport implementation is very stable. Of course, we didn't enter RC yet, so it's not obviously wrong for us to make such big changes. However, I realized it can be somewhat irresponsible action to our users who already are using MINA 2 in their production system. If they are going to spend many sleepless nights because of the radical changes, we're likely to lose a part of our precious community. Therefore, I thought it might be a better idea to maintain the current API and release GA as planned and to continue our experimentation in a separate branch. WDYT? Does it sound saner? :) Thanks, -- Trustin Lee - Principal Software Engineer, JBoss, Red Hat -- what we call human nature is actually human habit -- http://gleamynode.net/
signature.asc
Description: OpenPGP digital signature
