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

Re: 1.4.0 CHANGES - or: how to spend a weekend...

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-05-18 16:16:16 CEST

On 5/18/06, Peter N. Lundblad <peter@famlundblad.se> wrote:

> Someone needs to go through the logs between 1.3.0 was branched and
> HEAD, document most changes, except those that were backported to
> 1.3.x and those which weren't backported to 1.4.x. This will take
> some hours. Any takers? sussman?

Yes, it will take about 6 hours, based on the fact that I've done this
process for every release. Unfortunately, I don't have time to do it
this time around. :-( Would somebody else be willing to volunteer?

The process is basically:

1. Run 'svn log -rHEAD:16325
http://svn.collab.net/repos/svn/branches/1.4.x'. I think this
should give you every change ever made to the 1.4 line, including
backports made to the 1.4.x branch. But then, as Peter said, you need
to *remove* logs of changes that have already been released in 1.3.x
bugfixes. You can just run 'svn log -q --stop-on-copy' on the 1.3.x
branch, and then write a script to parse the revnums and remove them
from your primary log output. Karl and I used to use emacs macros to
do that. Maybe we should write a more general script. :-)

2. Read that log from oldest to newest, summarizing points as you go.
 The trick is to know what level of detail to write at: you don't
want to mention every tiny little commit, but you don't want to be too
general either. I usually set my filter-level by reading through a
few pages of the CHANGES file before I start writing the new one, just
to keep things consistent.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 18 16:16:50 2006

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