* Jeff Trawick wrote:
> On Fri, Aug 2, 2013 at 8:41 AM, Daniel Gruno <[email protected]> wrote:
> >
> > I'd like to change the note to something along these lines:
> > ----
> > mod_lua is in a state of continuous development. Usage
> > and behavior is subject to change at any time, even between stable
> > releases of the 2.4.x series. Be sure to check the CHANGES file before
> > upgrading
> > ----
>
> That text sounds fine but I don't see that as being reassuringly
> non-"Experimental" from the point of an enterprise distributor or a site
> administrator. Given that declaration, it would be naive to make your
> production site dependent on a fair amount of interesting code for
> mod_lua unless you think you can drop everything to tweak your scripts in
> order to pick up a httpd security fix at some arbitrary future time, or
> you can watch mod_lua development steadily to be prepared ahead of time.
> "Status: Experimental" is the flag we have to say "watch out for this
> module", which seems appropriate still.
+1.
If you want to break things AND be not experimental, do the changes simply
in trunk only (we've had that discussion...). Also, if I remember
correctly, there's a CTR policy for mod_lua/2.4.x in place, which needs to
be revoked once the module goes into a stable mode.
nd
--
package Hacker::Perl::Another::Just;print
qq~@{[reverse split/::/ =>__PACKAGE__]}~;
# André Malo # http://pub.perlig.de #
