[ANN] Release candidate for b 0.6 - call for testing
Michael Diamond
dimo414 at gmail.com
Sun Oct 30 07:45:59 UTC 2011
Hello all,
After a recent discussion on version control-tracked issues tracker (
http://mercurial.markmail.org/message/vv7ogjzi4al2c6co), lots of feedback,
and several excellent patches from the community, I've gotten around to
releasing a new version of b, the distributed issue tracker that's also a
Mercurial extension.
You can learn more about it here:
http://mercurial.selenic.com/wiki/bExtension and here:
http://www.digitalgemstones.com/projects/b/
The release candidate repository with the most up to date code can be found
here: http://hg.digitalgemstones.com/hg/b-dev/ - it seems largely stable to
me, but of course I would very much appreciate if anyone could help test it
with me. Barring any delays, the final release of 0.6 will be within the
week.
Primary changes since the last official release:
* Improved handling of repositories lacking issues directory - b should
work correctly whether directory exists or not
* Issues are automatically added (but not committed!) to Mercurial when
created
* Can now run commands by prefix, like Mercurial, 'hg b det 12' is
synonymous with 'hg b details 12'
* Editor config setting properly handles command line options now
* The primary issues file should always have the same structure, helping
minimize collisions and assisting in annotating and other data-mining.
* Output of 'hg b list' can now be sorted alphabetically and chronologically
* Improved error messages when user doesn't specify an issue ID
* Ability to specify an alternative revision with '--rev' to see issue
tracker status at that time
Current open issues:
f9 - b Should provide some way to check for empty resolutions -
http://hg.digitalgemstones.com/hg/b-dev/file/0.6.0-rc/.bugs/details/f930482615ce618feaff88cca7ec5d998dd6408f.txt
Request to optionally require users to enter details when resolving a
bug, or detect when they do not. Still considering options.
1 - Should output prefix of newly added bug if possible
Minor improvement to output of 'hg b add' - low priority
28 - missing unicode support
Handle unicode / other encodings of non-ASCII data more gracefully. At
present, b is fairly weak in this area, but identifying the right way to
solve the problem is slow.
I'd very much appreciate your feedback, and I hope you'll check it out if
you haven't before!
Michael
Michael Diamond
dimo414 at gmail.com
www.DigitalGemstones.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20111030/0a4c8521/attachment-0002.html>
More information about the Mercurial
mailing list