We're really close now to being able to ship a James 3 release. It's frustrating that work's still needed on the final assembly (of the application from the built server components). It looks likely that we're going to face ongoing maintenance issues (in this area) until improved tooling is developed.
ATM the assembly is included with the server modules, and released with them. Logically, though, assembly is a downstream process. Why not factor out assembly into a separate product (apache-james, say ;-) which is a downstream consumer of the server components? I think that this would allow us to start cutting 3.0.x releases of the server components immediately. The assembled application would be released when it's ready without the need to freeze server trunk. I think this this change would save me a lot of time in the short term, and (by moving towards continuous delivery) improve quality in the long term. Opinions? Objections? Robert --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
