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

Subversion issue tracker re-org

From: <cmpilato_at_collab.net>
Date: 2002-07-30 22:45:01 CEST

Back in the day (read, "just an hour ago") a person filing a new
issue against Subversion had two choices of what
component/subcomponent against which to file it:


Kevin Hancock <kevin@collab.net> has been kind enough to diversify our
options in this area now. We now have the components:


and then new subcomponents under each of those, allowing such combinations as:


The idea here is very simple (and was extremely useful to me at my
last place of employment). If I have been working in, say, libsvn_fs
for the past week, my brain is fully wrapped around that code. It
would be nice to query the issue tracker for all issues filed against
the 'subversion:libsvn_fs' component, to see if I can whip out other bug
fixes and features while my knowledge of the code is fresh.

I've already taken care of converting all whopping 5 'subversion:www'
issues to 'docs:www', so all that remains are the 'subversion:src' ones.
Now while I *could* fly through our 400+ issues (old and current) and
modify their component/subcomponent categorizations (and generate a
slew of mail as a result), I'm asking instead that folks make those
modifications as they update individual issues. If you're filing a
new Subversion bug, and have no idea where the fix might live, feel
free to use subversion:unknown -- someone (perhaps you) will later
diagnose the problem and be able to further specify the module that
needs a-fixing.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 22:46:27 2002

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.