And we went with Redmine (multi product support was a requirement). If you don’t need multi product support, I think Trac has the advantage that if/when Bloodhound becomes under active development, it is easy to make the switch. We never experienced any bugs with Bloodhound (v0.7 and v0.8) during the 6-12 months of using it, but we needed something that was regularly maintained so any bugs would eventually be resolved.
That aside, I think we as users are sometimes more demanding than fair. It is an open source project, and as far as I have understood it, all development (now) occurs on the developers' free time and without compensation. The nature of open source allows anyone to fix bugs, to their best of their abilities, which in turn allows you to patch issues that are important to you, but not prioritised by the core development team. (But for us who do not have the ability or time to do it - regular maintenance is a big thing) Sorry for the short rant, keep up the good work! Regards, > On 11 Sep 2015, at 08:28, Joseph D. Wagner <[email protected]> wrote: > > I went with Request Tracker. It has a different set of problems -- every > ticket system does -- but it seems more manageable and definitely has active > support. > > https://www.bestpractical.com/rt/ <https://www.bestpractical.com/rt/> > > In fairness to the BH team, this is a symptom of a systemic problem with > Apache projects that aren't considered "hip." > * James http://james.apache.org/ <http://james.apache.org/>. Email server > with no active development since 2012. It died right in the middle of > beta-testing it's next major release. > * SpamAssassin http://spamassassin.apache.org/ > <http://spamassassin.apache.org/>. No active development between 2011 and > 2014, but might be picking up again. > * Geronimo http://geronimo.apache.org/ <http://geronimo.apache.org/>. Java EE > 6 application server with no development since 2013. However, in Apache's > defense, it could be said that Oracle killed Java. > > Joseph D. Wagner > > On 09/10/2015 10:50 PM, Hoiniji Rosonye wrote: >> I think going to Trac is a good decision. With all due respect to the BH >> team, I think it still has a long way to go. I first gave BH a try, but it >> had too many bugs or configuration limits. I then decided to try Trac, and >> I found that it was very rock solid. >> >> On Sep 10, 2015 9:42 PM, "Torben Lauritzen" <[email protected] >> <mailto:[email protected]>> wrote: >> Hi. >> >> Thank you for your replies - I will go with the standard Trac for the moment >> then. But I will be following Bloodhound. >> >> /Torben >> >> > -----Original Message----- >> > From: Olemis Lang [mailto:[email protected] <mailto:[email protected]>] >> > Sent: 11. september 2015 05:57 >> > To: [email protected] <mailto:[email protected]> >> > Subject: Re: Is it alive? >> > >> > JFTR , I am working on a private fork of Bloodhound that I use for my >> > deployments . Nonetheless I've had to slow down my dev speed because I'm >> > contributing with code to the Brython project , and I've not had all the >> > time >> > I'd like these days for BH dev . >> > >> > >> > On 9/10/15, Ryan J Ollos <[email protected] <mailto:[email protected]>> >> > wrote: >> > > On Thu, Sep 10, 2015 at 6:38 AM, Torben Lauritzen <[email protected] >> > > <mailto:[email protected]>> wrote: >> > > >> > >> Hi. >> > >> >> > >> I was just about to install Trac, when I found Bloodhound. I have >> > >> tried installing it, and it seems ok. But at the same time it also >> > >> looks like the project is more or less dead - last release was >> > >> 2014-12-11, the documentation has unfinished things, e.g. the >> > >> section about git here: >> > >> https://issues.apache.org/bloodhound/wiki/BloodhoundInstall >> > >> <https://issues.apache.org/bloodhound/wiki/BloodhoundInstall> (the page >> > >> was last edited 7 months ago), there is a warning >> > >> (SubversionException) at the top of the Wiki pages etc. >> > >> >> > >> So, I just wanted to know if the project is still alive? Are anybody >> > >> working actively on the project? >> > >> >> > > >> > > Yeah there hasn't been much activity lately. I don't have any >> > > immediate plans or time to work on Bloodhound in the near future, but >> > > I'd be interested to hear if any other developers will be working on it. >> > > >> > > - Ryan >> > > >> > >> > >> > -- >> > Regards, >> > >> > Olemis - @olemislc >> > >> > Apache™ Bloodhound contributor >> > http://issues.apache.org/bloodhound <http://issues.apache.org/bloodhound> >> > http://blood-hound.net <http://blood-hound.net/> >> > >> > Brython committer >> > http://brython.info <http://brython.info/> >> > http://github.com/brython-dev/brython >> > <http://github.com/brython-dev/brython> >> > >> > Blog ES: http://simelo-es.blogspot.com/ <http://simelo-es.blogspot.com/> >> > Blog EN: http://simelo-en.blogspot.com/ <http://simelo-en.blogspot.com/> >> > >> > Featured article: >
