Hi, there are quite a few changes done to trunk in 3 months and I would consider to release a new rivet artifact.
A natural choice should be to label it 2.1.5, but the new policy for the request_rec pointer we carry around in rivet_globals prevents commands needing a valid record pointer from running. They now exit with a Tcl error (a test was added for that). Calling those commands outside of a request processing was an error anyway, still APR pool release policy didn't actually release memory every time. Thus pointers that were supposed to be dangling were left behind. Also the code was reorganized and various components (parser, uploads, channel..) are now in different directories, making possible to branch each of them separately from the rest of the code and still be able through configure to build a working module. I wonder if all this is enough for labeling the new release as 2.2.0 cheers -- -- Massimo Manghi Dipartimento di Neuroscienze Unità di Biofisica e Fisica Medica via Volturno 39 43125 Parma --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
