> Not really "working" on it yet. Just thinking and some offline > discussing with Martin last week. > Not sure, how we can easily manage this regarding SVN. > One plan is to implement/integrate as much as possible in current 1.1 > codebase as long as it keeps it compatible to 1.1. Some 1.2 goodies > are already implemented, right?
I agree this approach makes sense for now. Stuff like the client-side encryption are not addressed in 1.1 so adding them does not break anything. > Then we should make a 1.2 branch - is that the best practice? Yes eventually we will have to start a 1.2 branch. My thinking is that we hold off on this as long as possible. Its going to be a PITA to maintain both 1.1 and 1.2 codebases. By the time 1.2 branch starts we should have 99.9% of all 1.1 bugs fixed. At some point we should also decide to "freeze" the refactoring of 1.1. Remember when Mathias reworked the UIDataTable? (That was a great improvement BTW!) Once we start 1.2 things like that should be done in 1.2 only with 1.1 left as stable as possible. > How do other projects (eg Tomcat) start new spec implementations? I don't think there has been much work by Tomcact on the new JSP spec so far. I believe they are going to call their JSP 2.1 implementation Tomcat 6.x. My guess is that they are where we are. (Some offline discussions ... waiting for the spec to be final.) > One major issue with 1.2 is EL. Anybody knows about the status of the > Apache EL implementation? I have a question regarding the new EL. Does the old EL have to be supported still? It seems like a bunch of methods are *deprecated* but not removed. That's certainly going to complicate things in the interim. > Manfred sean
