+1 for having a roadmap to coordinate efforts and be able to plan ahead a bit. we can throw one up on the wiki.
+1 for doing an alpha release that includes the jsp/tags stuff. pulling out the jsp stuff is a feature subtract to the core, not a feature add. i think we should roll an alpha release before separating things. once we separate them, then we'll need to release two things (the JSP stuff and the core) before Tiles 2.x will be usable for most people. Releases aren't that hard, but i agree we should prioritize getting one out there (even if we can only label it as alpha). if Antonio wants to start pulling the JSP stuff out, we can always create a 2.0.x branch for the alpha release and let him work on the head. On 1/29/07, Greg Reddin <[EMAIL PROTECTED]> wrote:
I do think our highest priority right now should be moving towards a release. If this module separation can be done without hindering that goal, then I'm cool with it. However, we were thinking the introduction of the container would be the last big feature add before we try to release. So it leads me to wonder how many refactors/feature adds will we do before we roll it? I think if Antonio (and whoever else gets involved) can get the JSP module separated out pretty quickly, then we should do it and start immediately into the release process (whatever that ends up being). If it looks to be a big deal, then we should just go ahead and roll a 2.0.0 and do this in 2.1, IMO. The bottom line is that I think we need a roadmap and to try to stick to it as much as possible. Do we agree on that approach? Greg
