Hello everyone!
Weasel and I have upgraded https://trac.torproject.org to a newer version. Right now it has all of the functionality you were already accustomed to, but in the next few days it will get some more exciting features, like git integration. (I already verified that we are able to do it with our current git setup, but I will need to go through and poke at individual repos to make sure it works correctly.)
Right now I'm just starting with a small list: arm, tor-browser-bundle, obfsproxy, stem, tor, torbrowser, and torbutton. (I tried bridgedb but trac freaks out because it doesn't like something about that repo; I will try to figure out what's wrong after I finish these others).
If you want git integration for your repo(s), please file a ticket against the Trac component and I'll see what I can do!
Once the git integration works, we'll demo a code review tool (http://trac-hacks.org/wiki/CodeReviewerPlugin). I'll email again once we're further along with both of these processes. In the meanwhile, let me know if you run into any issues with the new trac.
Also, I would be remiss if I did not mention Mike's new favorite feature: a tag cloud. https://trac.torproject.org/projects/tor/tags
Thanks, Erinn (& weasel)
On Mon, 26 Aug 2013 22:45:20 +0200 Erinn Clark erinn@torproject.org wrote:
Hello everyone!
Weasel and I have upgraded https://trac.torproject.org to a newer version.
Thank you Erinn and weasel!
* Erinn Clark erinn@torproject.org [2013:08:26 22:45 +0200]:
Once the git integration works, we'll demo a code review tool (http://trac-hacks.org/wiki/CodeReviewerPlugin). I'll email again once we're further along with both of these processes. In the meanwhile, let me know if you run into any issues with the new trac.
So, git integration is working for several repos! i.e., when people commit and push changes, the source code browser on trac gets updated. You can see them here:
https://trac.torproject.org/projects/tor/browser
This isn't working for all branches in all repos yet, but as people return and begin committing more stuff, we can adjust appropriately. And again, if you want your stuff to be on this page, please let me know!
I've also just enabled the CommitTicketUpdater plugin, which allows you to close and reference tickets from commit messages. There are keywords that must be used to do this and for more information you can read all about it here:
http://trac.edgewall.org/wiki/CommitTicketUpdater
For quick reference:
Default values to close a ticket: close closed closes fix fixed fixes Default values to reference a ticket: addresses re references refs see
And then you use #nnnn syntax for the actual bug.
The CodeReviewerPlugin is installed, but requires changes to the way the CommitTicketUpdater works, so I'd rather wait and see how that works before proceeding to the next step. (You can read more about it here: http://trac-hacks.org/wiki/CodeReviewerPlugin)
Try it out and let me know if you have any issues!
-
Andrew Lewman -
Erinn Clark