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

Re: process for including changes in 1.0

From: <kfogel_at_collab.net>
Date: 2003-12-15 21:54:37 CET

"Erik Huelsmann" <e.huelsmann@gmx.net> writes:
> But they don't have repository wide log messages and revision
> numbers. And besides that: we would have everything about managing
> subversion issues in one place: what to fix and what to merge before
> a certain milestone will nicely be listed in one list when using the
> issue tracker.

The issue tracker is very nice for tracking each individual issue, and
for roughly comparing sets of issues by summary. It's not very good
for browsing a particular fact over all issues (such as the number of
votes it has). Issues are just not laid out right for this task.

As someone who's going to be spending a good part of the next few
weeks deeply immersed in the list of 1.0 candidate changes, I am
pretty sure I'll go crazy if that list is not in a text file :-). (I
don't mean to suggest that no one else will spend comparable time
immersed in the list, by the way... But I'll bet that those who do
will be thankful it's a text file too, in the end).

There are awkwardnesses both ways. There are some aspects of this
process that would be nice to have in the tracker, but they'll be in a
text file instead. C'est la vie. We don't have exactly the right
tool for the job here, so I'm trying to balance the tools we have to
get to a Point Of Least Pain.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 15 22:43:59 2003

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.