bugseverywhere - Bugtracker built on distributed version control

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merged with Trevor's -rr branch	Gianluca Montecchi	2009-10-02	2	-32/+6
\|
*	Added `be tag --list' to list all tags.	W. Trevor King	2009-06-25	1	-26/+5
\| \| \| \| \|	Loading all the bugs for the list search had the side effect of updating all the bug values files to the new YAML format.
*	Oops, dac91856-cb6a-4f69-8c03-38ff0b29aab2 was fixed with commit 242.	W. Trevor King	2008-11-23	1	-1/+1
\|
*	One of my tests left my bzr name as John Doe. Seems to be fixed now.	W. Trevor King	2008-11-18	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	I checked with $ python test.py ... $ ./test_usage.py ... $ hg showconfig \| grep ui.username && bzr whoami $ git config user.name && git config user.email && tla my-id
*	Major rewrite of RCS backends. RCS now represented as a class.	W. Trevor King	2008-11-18	5	-0/+113
	Lots of changes and just one commit. This started with bug dac91856-cb6a-4f69-8c03-38ff0b29aab2, when I noticed that new bugs were not being added appropriately with the Git backend. I'd been working with Git trouble before with bug 0cad2ac6-76ef-4a88-abdf-b2e02de76f5c, and decided things would be better off if I just scrapped the current RCS architecture and went to a more object oriented setup. So I did. It's not clear how to add support for an RCS backend: * Create a new module that - defines an inheritor of rsc.RCS, overriding the _rcs_() methods - provide a new() function for instantizating the new class - defines an inheritor of rcs.RCStestCase, overiding the Class attribute - defines 'suite' a unittest.TestSuite testing the module Add your new module to the rest in rcs._get_matching_rcs() * Add your new module to the rest in libbe/tests.py Although I'm not sure libbe/tests.py is still usefull. The new framework clears out a bunch of hackery that used to be involved with supporting becommands/diff.py. There's still room for progress though. While implementing the new verision, I moved the testing framework over from doctest to a doctest/unittest combination. Longer tests that don't demonstrate a function's usage should be moved to unittests at the end of the module, since unittest has better support for setup/teardown, etc. The new framework also revealed some underimplented backends, most notably arch. These backends have now been fixed. I also tweaked the test_usage.sh script to run through all the backends if it is called with no arguments. The fix for the dac bug turned out to be an unflushed file write :p.