Hi, There are currently 47 unresolved issues in our issue tracking system. IMO, they can be categorized into the following categories:
1) Bugs that needs fix https://issues.apache.org/jira/browse/DIRMINA-539 https://issues.apache.org/jira/browse/DIRMINA-574 These are known bugs so they need to be fixed before the GA release. 2) New features or improvement requests that require refactoring or API change https://issues.apache.org/jira/browse/DIRMINA-554 3) Others that don't require any API change All the other issues This means we have high possibility of reaching the first RC after three fixes. This is a good news for many those who use 2.0.0 milestones. If there's no noticeable issues with the RC, we can proceed to the first GA release of MINA 2. After then, we can keep adding bells and whistles in 2.1, 2.2 and so on. The reasoning behind this idea is to give users more chance to use MINA 2, which is a great step-forward comparing to MINA 1, and eventually will lessen our burden to maintain three branches at the same time. WDYT? -- 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
