in order to maintain the low volumes on this list and preserve it's use for high level discussion, development activity shifted to the server-dev list. but i think it might be useful to let everyone know now what's been happening and let people know about the short term roadmap. please feel free jump in with comments and suggestions.
the reorganisation into a separate subproject for mailet activity has continued. a new subsite is available at http://james.apache.org/mailet/ and the api is now located at http://james.apache.org/mailet/api/. the aim is to allow mailet products to be released independently from JAMES server and to encourage developers interested in mailets (but not JAMES server) to participate. ATM server-dev is used for mailet development activity but a separate development list may be split out later since the server-dev list is high volume. also new and cool is MailetDoc: a tool that creates documentation such as http://james.apache.org/mailet/standard/mailet-report.html the short term plan is to start releasing the new mailet components. first up is cutting a 2.4 release of the mailet API. this will be the first independent release and will differ from the 2.3 API shipped with JAMES server 2.3 only by a small number of minor bug fixes. JAMES server 3.0 and 2.x can then be consolidated onto the same mailet codebase. https://issues.apache.org/jira/browse/MAILET-15 has been created to track the release. development of this release will happen over on server-dev so if anyone's interested on this list please subscribe to the issue. this should be quickly followed by a crypto release. this will be the mature code base. once this is done, the improvements made on the development branch will be merged in. mailets remaining in trunk are tightly coupled to JAMES. one of the medium term challenges for the server team is to find a way to factor them out. ideas appreciated ;-) not much discussion about a next generation API :-/ - robert
