Daniel Perry wrote:
Check svn, last commit 12 days ago by Vincenzo, before that 2 weeks by Noel. Sure (some/all) of the committers might not be actively developing james, but they do commit patches with a bit of gentle persuasion :)
Unless you don't know the magic word and you solely rely on JIRA reports and posting on the mailing lists... Most proposed patches seem to be ignored.
Also, it seems to take a long time before comitted patches are actually released. There was a 2.2.1-rc1 release in August 2004. Whatever happened to next RC or the decision to make this one final?
James is stable, and I'd like to see it stay that way. I don't see a problem with relying on depreciated components when they are open source. They work. They have a proven track record. Sure, there wont be any development, but they work stably as is. If there's any urgent need to change anything in them, they're open source!
Yes, but no one dares to make a patched release of one of the deprecated components and incorporate it into James. I proposed a patch in the Phoenix container but it was very unclear if it could be part of a new James release.
I don't want to run a product where I have to apply my patches each time there is a new release.
Cheers,
Hes.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
