Re: [VOTE] Allow for defect fix releases at httpd
On 26 Apr 2018, at 8:51 PM, William A Rowe Jr <wrowe@xxxxxxxxxxxxx> wrote:
> With discussion exchanged (across several years), and various
> arguments presented, we should be able to adopt or reject the
> first of several possible questions as a PMC. This is the meta-
> question, any versioning discussion is irrelevant without specific
> purpose or goal, and follow on questions would decide how the
> PMC decides to solve this purpose;
In order to decide on anything, the following is needed:
- A clear description of what the problem is (a direct description, not an indirect reference to descriptions that have happened in the past).
- A clear proposal on what to do to fix the problem.
- A justification for the proposal demonstrating that the needs of all our users are acknowledged, understood and fully catered for, and the impact fully understood.
This last point above has been missing for me. Whenever this problem has been discussed, it has been brought to the table from a very narrow viewpoint, to solve a very specific problem that a specific person is having. The solutions have generally not taken into account the diversity of our user base, and usually solve a single problem while making other problems worse for others.
What has been missing is input from the major distributors of our software (Fedora, Ubuntu, Redhat, Debian, Apple, Windows, Linux from Scratch, etc), who I believe are probably going “httpd is a mature project, we have nothing to worry about”. I would recommend against making changes to our approach without soliciting the views of these people and making sure they’re all catered for.
Description: S/MIME cryptographic signature