[os-infrastructure] Bug/issue tracking (was commit messages)

[Grant Croker]

Bodo,

In principle I agree but what it should come down to is the best tool 
for the job, open-source solutions should be considered/evaluated along 
side their closed source counterparts.

If the SCM is Perforce then so be it, however the $200 price tag for 
every user might count against it. If you are aware of any open source 
bug/issue tracking software that be setup to support a paying/non-paying 
customer base then let the list know.

regards

grant

On 02/05/08 12:30, Bodo Bergmann wrote:
> JIRA is not Open Source.
>  
> I thought Subversion was selected because of it's the most common Open 
> Source SCM,
> otherwise we could also have selected Perforce - which is much more 
> Piccolo-like - due to its history/developers,
> so changing our processes using Perforce would a much easier task to do.
>  
> One of the arguments for Subversion was: It shows our commitment to 
> Open Source.
> If that is the case, we should continue this way when planning systems 
> for issue & bug tracking.
>  
> Bodo.
>
> ------------------------------------------------------------------------
> *From:* opensource-infrastructure-bounces at lists.ingres.com 
> [mailto:opensource-infrastructure-bounces at lists.ingres.com] *On Behalf 
> Of *Alex Hanshaw
> *Sent:* Friday, May 02, 2008 11:20 AM
> *To:* opensource-infrastructure at lists.ingres.com
> *Subject:* Re: [os-infrastructure] Bug/issue tracking (was commit 
> messages)
>
> I can see that it would be nice to be able to say we had JIRA running 
> on Ingres, but I do not see this as important.
> Outlook does not use Ingres as a repository but we use Outlook. RPM 
> does not use Ingres as a repository but
> that doesn't stop us  using RPM based distributions of Linux.
>
> Alex
>
> On Fri, 2008-05-02 at 11:03 +0200, Grant Croker wrote:
>> On 01/05/08 10:18, Andrew Ross wrote:
>> > The only issue I see is that Jira does not run on Ingres currently. I personally feel this is important. I don't think they would do a port just because. If we engage and show value/share some of the work, they may be interested in talking.
>> I never thought I would say this but I do not believe that not having 
>> Jira or whatever running on Ingres from day 1 is a problem. However the 
>> rollout of any system should include the plans/steps to port said system 
>> to Ingres. I guess this would be dependant on how willing Altassian (or 
>> whoever) would be to work with us to do a port and how much work would 
>> be involved. If there is functionality missing in Ingres that is 
>> required, how long would we be prepared to wait?
>>
>> g
>>
>>     
>
>
> Alex Hanshaw
> Manager, Sustaining Engineering
>
> *Ingres Corporation*
>
> _Alex.Hanshaw at ingres.com <mailto:first.last at ingres.com>_
> *PHONE*+44 1753 559515
> *FAX*+44 1753 559550
>
> *_www.ingres.com <http://www.ingres.com/>_*
>
> This transmission is confidential and intended solely for the use of 
> the recipient named above. It may contain confidential, proprietary, 
> or legally privileged information. If you are not the intended 
> recipient, you are hereby notified that any unauthorized review, use, 
> disclosure or distribution is strictly prohibited. If you have 
> received this transmission in error, please contact the sender by 
> reply e-mail and delete the original transmission and all copies from 
> your system.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> opensource-infrastructure mailing list
> opensource-infrastructure at lists.ingres.com
> http://lists.ingres.com/mailman/listinfo/opensource-infrastructure
>   


-- 
Grant Croker - Ingres PHP, Ruby and Python maintainer
Here the man in blue crimplene accosted us once more but we patiently
explained to him that he could **** off.