I’m good with making it the default. I still need to see if I can track down where that cacheing infinite loop was coming from, if it’s even still an issue. I say we shoot for February ’17. January is a bad month with everyone getting back from the holidays, and we need more eyeballs testing this before we push it.
I’m also excited about this change. It’s a big one, and a good one. It rips out a lot of custom C code in favor of very simple Tcl that does all the same things. Much more flexible, and it just FEELS more Tcl’ish. :) Damon > On Dec 5, 2016, at 3:58 PM, Massimo Manghi <mxman...@apache.org> wrote: > > Hi > > I hope nobody will mind if I set mod_rivet_ng as default build option for the > code in trunk. The code works pretty well and this model is so flexible that > I look forward to change my own sites so that the new Tcl based core > processing can be exploited to simplify installation and configuration. > > Damon, are you testing it on your development machine? What if we planned to > release rivet 3.0 in January/February 2017? > > > -- Massimo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org > For additional commands, e-mail: rivet-dev-h...@tcl.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
