on Sun Aug 28 2011, "Niall Douglas" <s_sourceforge-AT-nedprod.com> wrote:
> On 27 Aug 2011 at 12:29, Dave Abrahams wrote: > >> In that case, if I were you, I would actually start using Git with the >> modularized / CMake-ified Boost at http://github.com/boost-lib. > > If you do go for git, I have found repo embedded per-branch issue > tracking (e.g. http://bugseverywhere.org/) to be a god send for > productivity because you can raise issues with your own code without > bothering the mainline issue tracker about branch specific (and > indeed often personal) issues. It has made as much difference to my > productivity as adopting git did because I no longer need to keep > (and often misplace) post it notes reminding me of things to do. Last time I looked at BE it was not really ready for primetime. You're motivating me to check it out again. *checks it out* Hmm... not sure this will get beyond the personal, though: it lacks so much of what people have come to expect, like hyperlinking, and especially an *interactive* web interface for bug creation. > I even coded up a GUI for it for the TortoiseXXX family of revision > tracking GUIs which you can find at > http://www.nedprod.com/programs/Win32/BEurtle/. This lets you mark > off BE issue fixes with GIT/whatever commits. Cool! Maybe with your GUI it would be enough to get people to use it. Still needs a web interface for bug creation. I'm going to have to keep a closer eye on BE. -- Dave Abrahams BoostPro Computing http://www.boostpro.com _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
