Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CA+RK=_BDXmV1Hoxyqya52FmH6jbYOfXC9jdzNZ+=9_3Epm9LVw@mail.gmail.com>
References: <CAN5cbe6J1Pszy702tWQ2muu5K58hvCizyTRVhMQhdz98WKpz2w@mail.gmail.com>
 <CA+RK=_BDXmV1Hoxyqya52FmH6jbYOfXC9jdzNZ+=9_3Epm9LVw@mail.gmail.com>
From: Lars Francke <lars.francke@gmail.com>
Date: Thu, 30 Jun 2016 14:37:42 +0200
Message-ID: <CAD-Ua_g4ft2gYc4isSEns=zGOrjgM_iWJ2b72Qip=LWbwVaFGw@mail.gmail.com>
Subject: Re: [DISCUSS] issue trackers and recent stability of issues.apache/jira
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=001a114ba76c43f6c105367e257c
archived-at: Thu, 30 Jun 2016 12:38:33 -0000

--001a114ba76c43f6c105367e257c
Content-Type: text/plain; charset=UTF-8

JIRA is not always stable and that sucks but the cost of moving to a
different tool would be fairly high because lots of workflows we know about
(and probably more we don't) rely on JIRA (including my own). I'd be -0 on
changing especially if the issues can and will be resolved at some point in
the future.

On Wed, Jun 29, 2016 at 11:06 PM, Andrew Purtell <apurtell@apache.org>
wrote:

> JIRA identifiers in commits are essential for just about everything I do
> with HBase release management, maintenance, and operational support. I'm
> not opposed to switching to something else but then our backstory is split
> over (at least) two sources, without ease of cross-linking references.
>
>
> On Wed, Jun 29, 2016 at 1:06 PM, Sean Busbey <busbey@apache.org> wrote:
>
> > Heya folks,
> >
> > ASF hosted JIRA has had a rough go of things over the last few months.
> > Between the spam attacks impacting both availability and our usage
> > patterns and whatever has been causing the brown outs over the last
> > two days, things are impacting at least _my_ ability to make use of
> > the time I have available for the project.
> >
> > There are other options available to us as a project; no ASF policy
> > requires us to use any particular issue tracker or even an ASF hosted
> > issue tracker at all.
> >
> > Before I go through the effort to figure out what our requirements
> > would be for a third party solutions (in terms of user load,
> > persistence of messages, etc), what's our community temperature on
> > this issue? Do we have the stomach for a transition?
> >
> > -
> > busbey
> >
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

--001a114ba76c43f6c105367e257c--