I've created a new branch for the changes I'm about to start in on, for 5.4.
These are going to be pretty sweeping changes, and I expect a lot of (test)
instability for the duration.
I'm concerned about merging these changes back into master at the end of
the process. I don't want to freeze other work on the code base, but if
you think you're going to be doing more than minor surgery, it might be
nice to coordinate first on the dev mailing list.
I'm also concerned about the state of our documentation; these changes are
going to mean far, far more of our {since} caveats; I'm concerned that our
documentation will become a maze of these things! Having the ability to
create a parallel branch of the documentation (documentation as source
code, not as wiki pages) would be very nice.
Rolling up my sleeves ... ready to do some magic!
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
