bugseverywhere - Bugtracker built on distributed version control

	Commit message (Collapse)	Author	Age	Files	Lines
*	Updated copyright information	W. Trevor King	2010-01-01	1	-1/+1
\|
*	Added storage.Storage.storage_version() and command.InvalidStorageVersion.	W. Trevor King	2009-12-27	1	-2/+2
\| \| \| \|	Now commands automatically check for storage version compatibility.
*	Fixed libbe.storage.util.upgrade	W. Trevor King	2009-12-27	1	-2/+8
\| \| \| \| \| \| \| \| \| \| \| \| \|	Note that it only upgrades on-disk versions, so you can't use a non-VCS storage backend whose version isn't your command's current storage version. See #bea/110/bd1# for reasoning. To see the on-disk storage version, look at .be/version To see your command's supported storage version, look at be --full-version I added test_upgrade.sh to exercise the upgrade mechanism on BE's own repository.
*	Added libbe.version, wrapping the auto-generated libbe._version.	W. Trevor King	2009-09-15	1	-0/+50
	Two major benefits: 1) Programatic access to the BE version. Previously the version-string logic was internal to the commandline interface ./be, which left the other interfaces hanging. 2) Simple to override auto-generated revision id version with any string you like (by setting libbe.version._VERSION, if that's the way you want to run things or the way your packaging system requires. Note that other modules should never read libbe.version._VERSION, since it may not be defined. Instead they should use the output of libbe.version.version().