From: Trevor C. <pr...@se...> - 2003-07-30 19:24:10
|
I haven't seen this addressed recently, so I'm just curious on the current status. The most recent "detailed" info I could find was from Juergen's email on June 25 (http://sourceforge.net/mailarchive/message.php?msg_id=5357667), just before the 0.9 release. I have a few questions, partly to figure out if there's anything I'll be able to help with now (before September :) ) and also to gauge what to use for a project I'm starting. Anyway, here's my list of questions :) 1. What still needs to be done for 0.9.1. From that list, what is currently "assigned" to someone and what still needs help? 2. Same as #1 but for the 1.0 release. 3. What is the target time-frame for the 0.9.1 and 1.0 releases (obviously this is sketchy since it's "volunteer" work, but "gut guesses" - probably from Juergen :) - based on work left is what I'm hoping for. The previous estimate was the 1.0RC1 by now. 4. From Juergen's email which I referenced, it states "As far as I see, we don't need additional functionality for 1.0". The main thing holding me back from adopting the current code base (I'm currently using a personally-modified version of 0.8) is the amount and frequency of changes to core functionality and the public api. Some new features or minor bug fixes are ok/normal, but these sweeping changes are destructive to production code. How close are we to finalizing the public api and the core code? Is it likely that these major changes should be done for 0.9.1? To expand on my fourth question with a recommendation (hopefully it makes sense to everyone). If possible we should finalize the public api for version 0.9.1 rather than at the 1.0RC1. This will allow usage in new development without fear of incompatibilities in the next couple months. Personally this means I can use the current code base for development which will benefit me with the new features and bug fixes, it would benefit Spring by additional testing and use, and (on a personal note) it would allow me to start contributing again sooner (I don't have "spare time" until September, but I can use some "work time" once I'm using the current Spring version rather than 0.8). I believe I'm not alone in this, so hopefully a "mostly finalized" core will attract a bunch of new developers (either users or contributors) as well. Obviously this finalization would allow changes where required due to major gaffes and bugs (which I don't expect there will be too many of, but there's always some :) ). Trevor D. Cook |