Hi! I want to propose a Road-Map and ask about your opinions about some details. Most iportantly, I want to get up-to-date with the latest proceedings after being only physically but not mentally present in IRC :-)
I have made AxKit 5.8.0 clean, though it might require testing on 5.5. Commits follow these days when it runs fine for a few days. I propose to do a last this-pipeline-system release as CVS contains quite important bug fixes, IMHO, when these patches are in. After that, there are several options, and I'd like to hear your opinions: a) Bump version to 2.0 (optional), make it a mod_perl 2 module only, incorporate Mike's pipeline. Backwards compatibility (for authors of stylesheets, documents, taglibs and httpd.conf fully, for providers/language modules only partially) is planned but might take some beta versions to ensure. This way, people can use mod_perl 1 with the last 1.x release which will be maintained for some time, but only for bug fixes. This way, people still have a choice, but we will have less work as maintaining 1.x should be fairly simple - only bug fixes are backported. b) Merge the new pipeline like above into 1.x and begin developing a mod_perl 2 capable version, keeping AxKit fully dual-version. c) Make AxKit mod_perl 2 capable, do the pipeline stuff on a branch. My personal favourite is a), since if we risk breaking things, we should risk it heavily ;-) I don't think we have the manpower for the messiness of b), and c) would slow down the new pipeline stuff too much, IMHO. Also, as the new pipelining needs good testing, and mod_perl 2 needs it, too, we get two for the price of one. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
