"이희승 (Trustin Lee) <[EMAIL PROTECTED]>" wrote:
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.
yeah, this is a big move. We have to be careful, and it was a good move
to ask users and dev list about it.
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.
We did the very same mistake on ADS, telling our users "go for 1.5 !",
and now, we are in trouble. The thing is that the contract says :
"2.0-Mx are not stable versions", but 2.0-something looks like it's "API
frozen, bug fix expected"...
Of course, we didn't enter RC yet, so
it's not obviously wrong for us to make such big changes.
Exactly
However, I
realized it can be somewhat irresponsible action to our users who
already are using MINA 2 in their production system.
Well, irresponsible is a strong word. And going in production with
unstable versions is risky :)
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.
unless we help those guys and use them to see if our ideas are ok ...
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? :)
I would rather prefer going for 2.0 with the new features. We are in
may, then it's july, august, lot of vacations, slow business time, it's
might be a good window of opportunity.
IMHO, of course :)
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
