bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Dreimann <>
Subject Re: [ANNOUNCE] Apache Bloodhound 0.2 incubating Released
Date Thu, 15 Nov 2012 21:10:43 GMT
I think it may just be a time factor for all mirrors to update. I found the one below on the
page linked to in the announcement which seems to work:

I'll check again in the morning.

- Joe

@jdreimann - Twitter
Sent from my phone

On 15 Nov 2012, at 21:03, Gary Martin <> wrote:

> Hmm.. The link does not seem to work. I wonder if there is a step missed.
> The last release I did mention to infra that the files were ready to publish from the
dist directory but I have no idea if that is something required each time. I suppose it is
either that or it takes a while to propagate.
> Cheers,
>    Gary
> Joachim Dreimann <> wrote:
>> The Apache Bloodhound (Incubating) team is pleased to announce the
>> availability of the Apache Bloodhound 0.2-incubating release.
>> Apache Bloodhound is a project to provide a tool to track progress and
>> defects in projects, with a primary focus on software projects.
>> Standing on
>> the shoulders of the well-known Trac project, it will provide issue
>> tracking, repository browsing and a simple wiki syntax for easy
>> reference.
>> On top of this Bloodhound aims to provide intuitive support for
>> managing
>> multiple software projects, an advanced user-friendly interface and
>> simple
>> installation with some of the most important plugins for Trac available
>> by
>> default.
>> This is mostly a bugfix release, however the release notes can be
>> viewed at
>> the link below: [1]
>> The release can be downloaded from *
>> *
>> For further information on Apache Bloodhound, please visit the project
>> website at
>> The Apache Bloodhound Team.
>> [1]
>> Disclaimer:
>> Apache Bloodhound is an effort undergoing incubation at The Apache
>> Software
>> Foundation (ASF), sponsored by the Apache Incubator. Incubation is
>> required
>> of all newly accepted projects until a further review indicates that
>> the
>> infrastructure, communications, and decision making process have
>> stabilized
>> in a manner consistent with other successful ASF projects.  While
>> incubation
>> status is not necessarily a reflection of the completeness or stability
>> of
>> the code, it does indicate that the project has yet to be fully
>> endorsed by
>> the ASF.

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message