Re: [VOTE] Allow for defect fix releases at httpd
FTR I support moving to this versioning model.
I tend to think the best way to accomplish it, is to "just start doing
it". Tag 2.6.0. Then tag 2.7.0 when there are new features, etc.
Of course, our versioning docs don't support this model, but the docs
are a reflection of reality 15 years ago more so than current
attitudes. Make the docs reflect reality as it changes rather than
upfront votes unless absolutely necessary.
Is a vote like the above required to just start making minor releases
that contain new features, and making patch releases only contain bug
On Mon, Apr 30, 2018 at 9:26 AM, William A Rowe Jr <wrowe@xxxxxxxxxxxxx> wrote:
> On Thu, Apr 26, 2018 at 1:51 PM, William A Rowe Jr <wrowe@xxxxxxxxxxxxx>
>> [ ] The Apache HTTP Server project facilitates the release
>> of bug fixes to the current stable httpd release, correcting
>> defects to previously released code, excluding all new
>> features and enhancements. This is facilitated without
>> inhibiting development of new features and enhancements,
>> including the evolution release of candidates to the public
>> of new features and enhancements under consideration.
> As there are not three PMC members interested in delivering
> bug fix releases to our users, this question fails. I'm withdrawing
> any suggestion to find mechanisms to accomplish this goal.