Re: svn commit: r1735681 - /subversion/branches/1.9.x/STATUS
> Stefan Hett wrote on Tue, Apr 05, 2016 at 11:23:52 +0200:
>> Hi Stefan,
>>> On Mon, Apr 04, 2016 at 11:28:41PM +0200, Stefan wrote:
>>>> Should this be also nominated for backporting to the 1.8 branch, since the
>>>> issue has been reported in 1.8.11
>>> Officially, no. Because 1.8.x only receives fixes for security or data
>>> corruption problems at this point in time. The reporter of this bug has
>>> the option to upgrade to 1.9.x which is fully supported.
>>> Sometimes we're very nice and make exceptions. But that needs 3 or more
>>> people to invest some of their precious time which they could spend on
>>> trunk or 1.9.x instead. So it doesn't happen often.
>> Thanks for pointing that out.
> If you think it's important enough for 1.8.x, feel free to nominate it
> with my +1.
I just wasn't aware of the patch policy for 1.8. That's why I thought it
might have been overlooked.
That said: Thanks for the offer, but given the current patch policy, I
don't think the bug is "important" enough to deserve a special treatment.
Received on 2016-04-05 11:42:47 CEST
This is an archived mail posted to the Subversion Dev