Serge Knystautas wrote:
Noel J. Bergman wrote:
Really the biggest hurdle is a stable Avalon release. :)
I would use the latest release packages from Avalon, and once we get merged,
I think it makes sense for Stephen to add configuration files for a James
package using Merlin as well as our Phoenix packaging.
So to just get to a merged 3.0 release, we could do the following:
1. Move to latest release packages from Avalon.
2. Discuss and resolve the mailet API changes.
3. Address any discrepancies (code changes only applied to one or other, or otherwise require resolution).
Anything else?
Comments on feasibility:
If we have final releases from Avalon, then 1 is doable.
Everything from Avalon on which James is dependent has gone though an official release.
avalon-framework 4.1.5 (api & impl) cornerstone-threads 1.0 (api & impl) cornerstone-sockets 1.0 (api & impl) cornerstone-connection 1.0 (api & impl) cornerstone-scheduler 1.0 (api & impl) cornerstone-datasources 1.0 (api & impl) cornerstone-store 1.0 (api & impl) excalibur-collections 1.0 (single) excalibur-thread 1.1.1 (single) excalibur-pool 1.2 (single) excalibur-datasource-1.1.1 (single)
James is currently using the depricated Excalibur IO package. When preparing the cornerstone
relases I merged some of the utility classes so that you would have a drop dead easy migration
solution. I'll need to dig back into cornerstone to clarify that (but its a minor point).
Cheers, Steve.
I think we have some consensus about 2... we originally were planning more sweeping changes and include repository changes, but I don't know if that is appropriate since we're still stuck on the IMAP changes.
Then 3 is just thankless grunt work.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
