You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Thilo Goetz <tw...@gmx.de> on 2006/11/15 16:02:32 UTC
Jira for minor issues?
I updated our website to fix a broken link without a Jira issue (didn't
really think about it). What's everybody's opinion, should we have a
Jira issue for every SVN change, or do we fix trivial issues without a
Jira ticket? I have no strong opinion, I'm used to having to open a
ticket for absolutely everything. On the other hand, it does seem like
a bit of overkill. Thoughts?
--Thilo
Re: Jira for minor issues?
Posted by Michael Baessler <mb...@michael-baessler.de>.
I'm also think it is better to have a JIRA issue for all changes.
-- Michael
Marshall Schor wrote:
> I agree. -Marshall
>
> Thilo Goetz wrote:
>> Adam Lally wrote:
>>> On 11/15/06, Thilo Goetz <tw...@gmx.de> wrote:
>>>> I updated our website to fix a broken link without a Jira issue
>>>> (didn't
>>>> really think about it). What's everybody's opinion, should we have a
>>>> Jira issue for every SVN change, or do we fix trivial issues without a
>>>> Jira ticket? I have no strong opinion, I'm used to having to open a
>>>> ticket for absolutely everything. On the other hand, it does seem
>>>> like
>>>> a bit of overkill. Thoughts?
>>>
>>> I think for really trivial stuff like this it's OK not to have the
>>> JIRA issue. But I think this should be done rarely. Once we have a
>>> user base, I think we'll want to have a JIRA issue for anything a user
>>> might conceivably report as a problem, so that users searching the
>>> JIRA can find that we've already addressed the problem.
>>>
>>> -Adam
>>
>> Good point, I hadn't thought of that.
>>
>> --Thilo
>>
>>
>>
>
>
>
Re: Jira for minor issues?
Posted by Marshall Schor <ms...@schor.com>.
I agree. -Marshall
Thilo Goetz wrote:
> Adam Lally wrote:
>> On 11/15/06, Thilo Goetz <tw...@gmx.de> wrote:
>>> I updated our website to fix a broken link without a Jira issue (didn't
>>> really think about it). What's everybody's opinion, should we have a
>>> Jira issue for every SVN change, or do we fix trivial issues without a
>>> Jira ticket? I have no strong opinion, I'm used to having to open a
>>> ticket for absolutely everything. On the other hand, it does seem like
>>> a bit of overkill. Thoughts?
>>
>> I think for really trivial stuff like this it's OK not to have the
>> JIRA issue. But I think this should be done rarely. Once we have a
>> user base, I think we'll want to have a JIRA issue for anything a user
>> might conceivably report as a problem, so that users searching the
>> JIRA can find that we've already addressed the problem.
>>
>> -Adam
>
> Good point, I hadn't thought of that.
>
> --Thilo
>
>
>
Re: Jira for minor issues?
Posted by Thilo Goetz <tw...@gmx.de>.
Adam Lally wrote:
> On 11/15/06, Thilo Goetz <tw...@gmx.de> wrote:
>> I updated our website to fix a broken link without a Jira issue (didn't
>> really think about it). What's everybody's opinion, should we have a
>> Jira issue for every SVN change, or do we fix trivial issues without a
>> Jira ticket? I have no strong opinion, I'm used to having to open a
>> ticket for absolutely everything. On the other hand, it does seem like
>> a bit of overkill. Thoughts?
>
> I think for really trivial stuff like this it's OK not to have the
> JIRA issue. But I think this should be done rarely. Once we have a
> user base, I think we'll want to have a JIRA issue for anything a user
> might conceivably report as a problem, so that users searching the
> JIRA can find that we've already addressed the problem.
>
> -Adam
Good point, I hadn't thought of that.
--Thilo
Re: Jira for minor issues?
Posted by Adam Lally <al...@alum.rpi.edu>.
On 11/15/06, Thilo Goetz <tw...@gmx.de> wrote:
> I updated our website to fix a broken link without a Jira issue (didn't
> really think about it). What's everybody's opinion, should we have a
> Jira issue for every SVN change, or do we fix trivial issues without a
> Jira ticket? I have no strong opinion, I'm used to having to open a
> ticket for absolutely everything. On the other hand, it does seem like
> a bit of overkill. Thoughts?
I think for really trivial stuff like this it's OK not to have the
JIRA issue. But I think this should be done rarely. Once we have a
user base, I think we'll want to have a JIRA issue for anything a user
might conceivably report as a problem, so that users searching the
JIRA can find that we've already addressed the problem.
-Adam