[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-dev
Subject:    Re: [VOTE] Allow for defect fix releases at httpd
From:       Eric Covener <covener () gmail ! com>
Date:       2018-04-30 18:32:29
Message-ID: CALK=YjPffZr9r4ZtryVJWDV_1vFdn1bAuLjhFFQtbRAe=0P+Cw () mail ! gmail ! com
[Download RAW message or body]

On Mon, Apr 30, 2018 at 2:21 PM, Paul Querna <paul@querna.org> wrote:
> 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
> fixes?

I think something is needed to avoid other parts of the team putting
enhancements into 2.4 at the same time, or from throwing up their
hands at the prospect of N streams / STATUS files.
[prev in list] [next in list] [prev in thread] [next in thread]