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

Re: Merge bug -- svn:keywords and conflict resolution

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 31 May 2012 16:57:55 -0400

On Thu, May 31, 2012 at 4:54 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> On Thu, May 31, 2012 at 2:53 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>>
>> I do not think it will ever happen though because generally Red Hat is
>> only going to backport fixes that have been deemed critical to
>> security.
>
> That's really an overgeneralization - they do that within minor
> release versions, but when the minor number changes, updates with less
> critical fixes and even new features may be included.   For example
> RHEL 5.0 was released with a subversion 1.4.2 build, but by 5.6 it was
> up to 1.6.11.   So it isn't really set in stone that 1.6.x will be
> kept into the distant future in the 6.x distribution either.   But, I
> thought 1.4.x was kept for a painfully long time and don't know how
> the decision is made to bump application revision numbers.

It seems to me that once they settle on a version like 1.6.11 that
after that you do not see them move up to 1.6.17 or 1.6.18. Instead
they seem to pull in high value fixes to their own custom 1.6.11.xxx
version. Eventually they jump up to a 1.7.x or 1.8.x release and
repeat the process.

I am just saying that if we released a 1.6.20 or 1.6.21 etc. that it
seems unlikely they would just jump to that release as a whole. If
they are going to selectively backport fixes then it seems like the
best process is to open a bug with them to request a fix be backported
and then lobby as needed.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2012-05-31 22:58:28 CEST

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