incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olemis Lang <ole...@gmail.com>
Subject Re: [podling setup] Bloodhound alternative for issues
Date Sun, 14 Apr 2013 23:04:33 GMT
On 4/10/13, Christian Grobmeier <grobmeier@gmail.com> wrote:
> Hi,
>

:)

> we suggest using Jira or Bugzilla for new podlings:
> http://incubator.apache.org/guides/proposal.html#template-issue-tracking
>
> But we have Apache Bloodhound, and they have an installed instance here:
> https://issues.apache.org/bloodhound
>
> I am not sure if it is ready for other projects, but can imagine.
> Anybody knows about the status?
>

The current state of the instance deployed in there is still focused
on hosting a single product (i.e. project) as we are running 0.4.0 .
We are in the process of publishing bug fix release 0.5.3 . While
running that version the situation will be exactly the same .

Multi-product support however is the main target for next major
version . As such, it has been committed into trunk and we are
actively working in the following directions :

  1. Unit and functional testing
  2. Improve support for DB backends (e.g. PostgreSQL)
  3. Data migration (JIRA, single-product Trac / Bloodhound upgrades)
  4. Usability details
     * notably those related to establishing a clear distinction
       between site admins (e.g. infra) and product admins (e.g.
       PMC power users)

Personally , I'll start to use trunk version on my own shortly after
some changes will be committed . Overall it's looking good enough to
try it .

So , ASF deployment for new podlings will be possible after releasing
version 0.6.0 (or 1.0 , depending on what version number is coming
next ;) . At that time the issue tracking platform and tools will be
ready for use by new podlings. Shortly after that milestone existing
TLP might even be able to migrate from JIRA if considered appropriate
. Support for migrating data hosted by other issue trackers will take
a little bit longer. Should anybody be interested on one such
migration (Bugzilla, Scarab, ...) please let us know.

> If it is ready for us I think we should invite podlings to use
> Bloodhound - and maybe even suggest Bloodhound as first idea.
>

We are very excited about the possibility of using it to assist ASF
communities in the process of «creating high quality software that
leads the way in its field» . One such deployment will be quite
important for us to gather feedback and improve the solution we've got
. The Bloodhound community will always welcome request for
enhancements and will be there for you to fix issues as soon as
possible .

> Thoughts?
>

It's worth to mention that even after all this happen there will be
limited or no support to connect the repository browser to the
repository at svn.apache.org . It all depends on the progress we can
make working on #478 [1]_ .

On the other hand it will be possible to do so for `git` repositories
. Based on my previous experience using Trac + Git this will actually
work . Beware of the fact that there's a lot of room for improvements
, especially when dealing with (big / huge) git repositories .

.. [1] SVN pubsub integration
       (https://issues.apache.org/bloodhound/ticket/478)

-- 
Regards,

Olemis.

Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message