>> From my point of view the most important point is to describe what >> James does now. > > +1
Yes, I agree. Again, I do not disagree that this is “most important”. Let me use a more concrete example to illustrate why it is not the **only** concern. When I first looked into James, there was a complex grid to choose from between Spring and Guice. Based on the grid, it seemed to me that Spring was better. When I started asking questions, though, I understood that Spring is not really being maintained anymore, or at least, more energy is being put into Guice. Well, for me as a user trying to understand what to do, that is pretty darn important information! I **WANT** to know where the project is heading, because I need to be able to make decisions. So not only do I need to know what the project’s vision is (which IMO needs a lot of clarification currently), I need to know more concretely what the plans are for at least the next major release. Else, how can I decide if it’s worth investing or not? On that note, I would propose that for the 4.0 release, we clearly indicate that Spring will **NOT** be available. It should be deprecated in an upcoming 3.x release, then “completely” eliminated in 4.0. (Perhaps some code could remain if some people really want it, but we need to make it clear in the “user contract" that it is not supported.) That would be precisely what a major release is for, IMO. Thoughts? =David --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
