> > > > Check SVN, last commit 12 days ago by Vincenzo, before that 2 > > 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.
Fair enough. You'll find with many open source projects that if you want a current (albeit unstable) version, then you have to dig into cvs/svn. I haven't got the hang of SVN just yet... but viewcvs makes it easier! I agree with the comments about JIRA/mailing list. I think JIRA needs to be more used, as it helps keep things more organised/accessible. I am guilty of sending patches/comments to the mailing list that really should be in JIRA. Obviously putting everything into JIRA isn't the solution, as people (committers) need to be reviewing the JIRA requests, and reviewing code, commenting, and where appropriate committing the code to SVN. > Also, it seems to take a long time before committed 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? Fair comment. Is there a need for a release? Has anything much changed since rc1? > 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. Why not? I don't see a problem with patching deprecated components. In fact, once they're deprecated, there's no longer any reason to go through the steps trying to get it incorporated in the proper component. > > I don't want to run a product where I have to apply my patches each time > there is a new release. This I totally agree with. I have issues with james (stock build) that I have to patch each time I update the system. This is a pain in the ass. I'm sure some of the patches would be useful to some other people, although also harmless to everyone. Some of them are for our setup, so they shouldn't be committed. I would like to see james development shift up a gear, and james evolve into a better product. There seem to be developers about that are producing useful code that could be contributed back to the project, that we are missing out on. Daniel. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
