Re: [C++-sig] [Boost.Python v3] Planning and Logistics
on Sun Aug 28 2011, "Niall Douglas" 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 [email protected] http://mail.python.org/mailman/listinfo/cplusplus-sig
[C++-sig] Off-topic: Personal bug tracking (was: Re: [Boost.Python v3] Planning and Logistics)
On 3 Oct 2011 at 8:34, Dave Abrahams wrote: > 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 agree it isn't fit to go beyond the personal. I'd even say, actually, that when you go beyond bug tracking within a (very) small group it's time for Redmine or Trac. I'd also say personal bug trackers are much more of a design/development tool than a deployment/support tool. They're really a type of post-it note tied into the repository. As I know you know Dave, you also often get emails containing good ideas for some software project of yours, but right now you don't have the time to really look into them. Here BE also excels - you dump out the email and attach it to a BE feature issue. That prevents you forgetting about them, or much later on wasting time searching your email not quite remembering the correct search terms. > > 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. I develop for Windows first and POSIX later, so something which integrates into the Tortoise family of SCM GUIs is much more important to me than a web interface. I really, really wish KDE would integrate proper multi-SCM support into itself too. I agree though that a JSON-RPC interface to BE would be a very useful addition, not just to aid BEurtle's performance, and of course from that a dynamic web interface becomes much easier. My thread regarding the topic (http://void.printf.net/pipermail/be-devel/2011- September/thread.html) went nowhere though. Again, I might add the support myself for the next BEurtle release and upload it as a fork to pypi as BE's author is unwilling to permit BE to go onto pypi. [BTW to anyone interested, my GUI needs a new release as several show stopping bugs have since been found. Hopefully I'll get a chance before Christmas, meanwhile GIT HEAD has already fixed the worst of them] Niall -- Technology & Consulting Services - ned Productions Limited. http://www.nedproductions.biz/. VAT reg: IE 9708311Q. Company no: 472909. ___ Cplusplus-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/cplusplus-sig
Re: [C++-sig] Off-topic: Personal bug tracking
on Mon Oct 03 2011, "Niall Douglas" wrote: > On 3 Oct 2011 at 8:34, Dave Abrahams wrote: > >> 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 agree it isn't fit to go beyond the personal. I'd even say, > actually, that when you go beyond bug tracking within a (very) small > group it's time for Redmine or Trac. > > I'd also say personal bug trackers are much more of a > design/development tool than a deployment/support tool. They're > really a type of post-it note tied into the repository. I'd like to try it. But now, suppose you have a project on github and you want to make it easy for people to report bugs. Clearly you need to enable the GitHub issue tracker, right? How do you integrate that with your be workflow? > As I know you know Dave, you also often get emails containing good > ideas for some software project of yours, but right now you don't > have the time to really look into them. Here BE also excels - you > dump out the email and attach it to a BE feature issue. That prevents > you forgetting about them, or much later on wasting time searching > your email not quite remembering the correct search terms. Yeah, I can see the appeal. >> > 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. > > I develop for Windows first and POSIX later, so something which > integrates into the Tortoise family of SCM GUIs is much more > important to me than a web interface. I really, really wish KDE would > integrate proper multi-SCM support into itself too. > > I agree though that a JSON-RPC interface to BE would be a very useful > addition, not just to aid BEurtle's performance, and of course from > that a dynamic web interface becomes much easier. My thread regarding > the topic (http://void.printf.net/pipermail/be-devel/2011- > September/thread.html) went nowhere though. Again, I might add the > support myself for the next BEurtle release and upload it as a fork > to pypi as BE's author is unwilling to permit BE to go onto pypi. Seriously? That's not a very good sign. Why not? I found installing BE to be a bit of a struggle. -- Dave Abrahams BoostPro Computing http://www.boostpro.com ___ Cplusplus-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/cplusplus-sig
