bugseverywhere - Bugtracker built on distributed version control

	Commit message (Collapse)	Author	Age	Files	Lines
*	Converted libbe.storage.vcs.base to new Storage format.	W. Trevor King	2009-12-13	4	-21/+0
\|
*	Added libbe/upgrade.py to handle upgrading on-disk bugdirs.	W. Trevor King	2009-08-31	2	-6/+6
\|
*	Went through "closed" bugs looking for miss-categorized bugs.	W. Trevor King	2009-07-11	2	-32/+6
\| \| \| \| \| \|	Found a few that were actually "fixed" and one that I reopened. Perhaps we should add a "merged" status to the default, so that the merged bugs don't clutter up the closed bugs category...
*	Another major rewrite. Now BugDir, Bug, and Comment are more distinct.	W. Trevor King	2008-11-21	2	-0/+14
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I pushed a lot of the little helper functions into the main classes, which makes it easier for me to keep track of what's going on. I'm now at the point where I can run through `python test.py` with each of the backends (by changing the search order in rcs.py _get_matching_rcs) without any unexpected errors for each backend (except Arch). I can also run `test_usage.sh` without non-Arch errors either. However, don't consider this a stable commit yet. The bzr backend is reallyslow*, and the other's aren't blazingly fast either. I think I'm rewriting the entire database every time I save it :p. Still, it passes the checks. and I don't like it when zounds of changes build up.
*	Closed the bug for adding tests	Aaron Bentley	2005-03-24	2	-0/+15
\|
*	Finished tests for new	Aaron Bentley	2005-03-24	2	-0/+18