[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Start using RCs (Was: Re: So... when should we do 2.4.34? [WAS: Re: Revisit Versioning? (Was: 2.4.3x regression w/SSL vhost configs)])

Unhelpful for whom? If we ship the latest, secure config from the single release branch, we wouldn't be encumbered by having to use tricks for fixes. Most end users who get their custom build from the distros would get the same custom directive-level fixes applicable to them (ie:  they know what's in the build so don't have to do such gymnastics).

In the same vein of thought, if it is disruptive to a config, that signals a minor bump. Patch changes must be forward compatible.
Daniel Ruggeri

On April 22, 2018 12:32:24 PM CDT, Eric Covener <covener@xxxxxxxxx> wrote:
>On Sun, Apr 22, 2018 at 1:31 PM, Eric Covener <covener@xxxxxxxxx>
>>> I'd further add that no directives are added in
>>> patch releases, but minor releases would be fair game.
>> I don't think that kind of rule would be helpful, it just pushes
>> configuration into defines, per-request environment variables, etc
>> which are worse (because unlike a directive, you can't tell if
>> present)
>Of fixes which may be disruptive, that is.

( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache2-developers/msg03869.html on line 88
Call Stack
10.0007364672{main}( ).../msg03869.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache2-developers/msg03869.html on line 88
Call Stack
10.0007364672{main}( ).../msg03869.html:0