Hi,

I only speak about bug report/patchs for GLPI. 

Plugins have their own worklow.


Le mar 21/06/11 10:06, Emmanuel Lacour elac...@easter-eggs.com a écrit:
(...)
> but makes hard to track those bugs, find them, reference them, etc...

Not at all. Each confirmed bugs are report on the bug tracker. It's only a 
pre-validation....

> many free software projects uses bug trackers without much difficulty.
> even some managed by a small sized company.

And ? Please don't use this kind of argument. It's a very bad way to justify 
anything...

We seem perhaps idiots but we  have already try this workflow and the 
bugtracker became an awfull piece of shit with a 
ununderstandable, incomplete, wrong, french, spanish, italian   reports etc...

So for our confort and health we have choose the actual process.

 
> it should be enough to just request users to create a redmine account
> (with captcha in register page) before being allowed to report bugs.

We use captcha on the forum and we have a lot of spamers that register anyway.

> it should force users to think a little bit before reporting bugs (...)

In god you trust !

(...)

> to be explicit, my current deal is that I have a customer that gives
> me money to fix glpi bugs he found and it's just a pain for me to submit
> patches and to follow their inclusion in svn.

So this is a real need. 

Two ways :

- Submit your patch on the dev mailing list, you would have an answer and a 
developper would give you the ticket number on the bug 
tracker. You could folllow the treament of the ticket. it's seems to be very 
easy...

- Register on the forge and ask for a bugtracker access. But if you do wrong 
things, you will be fired ;)

Best regards,

--
Jean-Mathieu Doléans
GLPI-PROJECT.ORG






_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev

Reply via email to