[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: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2006-05-19 20:58:37 CEST

Ben Collins-Sussman wrote:
> On 5/18/06, Nicolás Lichtmaier <nick@reloco.com.ar> 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?
>>>
>> Sorry to interrupt but... wouldn't it be better to write this document
>> side by side with the changes? This is what I see it's being don in gcc
>> (see http://gcc.gnu.org/gcc-4.2/changes.html). When important things get
>> done, this document would be updated. It's nicer to users and it helps
>> to have a clear view of which things have been done of the current
>> release. Just an idea.
>>
>
> The reason we don't do it that way is because the CHANGES file is more
> coherent if written by a single author, working at a single level of
> 'filtering'. (The gcc file you link to is extremely general, by the
> way. We operate at a lowel level of detail.)

In addition, as a gcc developer, i can tell you the changes file is
rarely updated for major changes unless someone is poked as a reminder
to add stuff to it after their commit.

In fact, recently, changes.html has been cribbed from the wiki's
projects page that describes the main projects that were going on at the
time.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 19 20:59:21 2006

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