[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 23:28:34 CET

Ben Reser <ben@reser.org> writes:
> Maybe the issue tracker should have some sort of voting system added to
> it? Obviously doesn't help us now. Mandrake added such a thing for
> its bugzilla and it's pretty handy.

Funny you should mention that. I'm sitting here looking at my issues
summary, and realizing that the Status field is actually not a bad
place for this. We've only used it for effort estimates up till now,
but it could hold vote totals.

Everything else about an issue summary is perfect for the task: we've
got the P number, the milestone ("1.0" in this case, with option to
move to "1.2" or "Post-1.0" if the votes don't reach the threshold).
Maybe I'm wrong, and this isn't so much less convenient than a text

Well, what the heck. It seems most people prefer the issue-based
solution, or are at least okay with it; I'm the one being picky here.
Let's try using the issue tracker and see if it works. If it's too
painful to be borne, we'll notice pretty quickly.

I'll update HACKING.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 16 00:17:33 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.