[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1845378 - /subversion/trunk/CHANGES

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 02 Nov 2018 02:56:25 +0000

Branko Čibej wrote on Wed, 31 Oct 2018 21:10 +0100:
> On 31.10.2018 21:08, Daniel Shahaf wrote:
> > Other issue: In the three months centered on the 1.12.0 release we'll be
> > supporting 1.9, 1.10, 1.11, 1.12, and trunk in parallel, so I think we
> > should reduce the CHANGES management effort. To take this commit as an
> > example, while brane added a line to the 1.12 CHANGES, the RM's of 1.9,
> > 1.10, 1.11 will have to copy it manually. That adds up.
> Nope, they will not; this change will not be backported.

I said, to take that commit "as an example". My point was that we need
to think about reducing the CHANGES maintenance overhead; whether
any particular commit does or does not require backporting is besides
that point.
Received on 2018-11-02 03:56:35 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.