Hello James Devs, Please vote on the following issues. This is a lazy consensus vote starting now, ending in 72h.
I propose the following new changes to James mailets: New project names: Apache James :: Mailets Parent .................... SUCCESS [3.814s] Apache James :: Mailet API ........................ SUCCESS [0.200s] Apache James :: Basic Mailet Toolkit .............. SUCCESS [0.184s] Apache James :: Mailetdocs Maven Plugin ........... SUCCESS [2.274s] Apache James :: Crypto Mailets .................... SUCCESS [0.168s] Apache James :: Standard Mailets .................. SUCCESS [0.307s] Apache James :: AI Mailets ........................ SUCCESS [0.017s] Apache James :: Classic AI Mailets ................ SUCCESS [0.189s] Apache James :: Mailets Aggregator ................ SUCCESS [0.019s] New artifactId's and versions: ** all have groupId org.apache.james apache-james-ai-project-0.1-SNAPSHOT -> apache-mailets-ai-0.0.1-SNAPSHOT apache-james-ai-classic-0.1-SNAPSHOT -> apache-mailets-ai-classic-0.0.1-SNAPSHOT mailet-project-1-SNAPSHOT -> apache-mailets-0.0.1-SNAPSHOT (this is parent -- will contain all mailet specific project info and depend on james-project-1.8.1 -> all other mailets will depend on apache-mailets) apache-mailet-2.5-SNAPSHOT -> apache-mailets-api-2.5.0-SNAPSHOT apache-mailet-base-1.2-SNAPSHOT -> apache-mailets-base-1.2.0-SNAPHSOT apache-crypto-mailets-1.1-SNAPSHOT -> apache-mailets-crypto-1.1.0-SNAPSHOT maven-mailetdocs-lugin-0.2-SNAPSHOT -> changed version to 0.0.2-SNAPSHOT mailet-project-1.0-SNAPSHOT -> apache-mailets-aggregator-0.01-SNAPSHOT All chages are available as a github commit [1]. Further proposed changes TBD - will go on JIRA: * change directory names to mailets-<current-name> (not strong opinion) * clean-up 1: agggregate all project info, dependencies and other stuff to parent apache-mailets and remove duplication -- A MUST DO * move site related content under site -- A MUST DO IMHO * aggregate JIRA tracking under the same project - going through the project I noticed each mailet has it's own JIRA project, mailinglist, etc. I think it's a lot of overhead and not worth it. The community is not that big. I also think less is more. -- also a MUST DO IMHO * move code to java 1.6 (which will be end-of-life in spring 2013) - like all other James code * make a release and publish site [+1] Yes, I agree [0] No time to review, [-1] No I don't agree -- Ioan Eugen Stan / CTO / http://axemblr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
