On Thu, Mar 26, 2015 at 2:26 PM, Charles Benke <charles...@benke.fr> wrote:
> Hello,, > > I think we need to simplify the bug report the more as possible and use > github is not simple for simple users > > Please consider that Dolibarr users are not all developer with a github > account > > A good way for reporting bug is a simple form with a feature of attached > picture on the Dolibarr main website (org, fr, …) > > It’s not the job of an user to make the job of a developper > > I think this can be solved by makeing available a page in Dolibarr itself. Which would have the ability to post directly to github as a dolibarr or whatever user. Sometimes users which do not have development skills can report something as a bug but in reality its just a missing functionality or they do not know how to do it. Rgds Saxa > > > Bien cordialement, > > Charles-François BENKE > > > > *De :* dolibarr-dev-bounces+charles.fr=benke...@nongnu.org [mailto: > dolibarr-dev-bounces+charles.fr=benke...@nongnu.org] *De la part de* > Laurent Destailleur (aka Eldy) > *Envoyé :* jeudi 26 mars 2015 16:08 > *À :* ML Dolibarr dev > *Objet :* [Dolibarr-dev] New rule to report bug and task > > > > Few days ago, we decided to abandon our current bug and request tracker to > follow Dolibarr bugs and features requests. > > > > You must use now the Issue tracker of Github. > > You will find here: https://github.com/Dolibarr/dolibarr (click on link > "Issue" on left of page). > > > > Also don't forget to set tags on your report to qualify your report. > > > > > > > > WHY A NEW TRACKING SYSTEM ? > > > > Using the old tracker was just a pain for several reasons : > > > > * When closing a bug, we had to close the bug manualy into the bug > tracker. It wasn't done or when done, it was a lot of waste ot time. This > is past, now closing a bug into github with "Closed #xxx" into the > description of the change automatically close the bug. > > > > * The id of bug reported into the comment of github was an id into another > system. So switching to code from ticket or to ticket description from code > was just awful. Now, one click is enough. > > > > * The old tracker was not public and not visible. You had to create an > account making the bug and feature tracker difficult to use for "quick > report". > > > > * Our old tracker had a very bad visibility. I hope this will change. > > > > * Our old tracker was maintained by the Dolibarr foundation. This need a > lot of time spent by the core team. Removing completely this tasks should > provide more free time us. > > > > * Integration with IDE tools like eclipse was difficult. You may find > plugins more easily with github. > > > > > > > > WHAT ABOUT OLD TICKETS: > > > > * That is the negative point. But i think we must accept this to progress: > Old tickets still opened, like closed one will just be forgotten. We will > enter them back into new GitHub tracker day by day. > > > > > > > > Enjoy our new tracking system. Who wil be the first to enter one issue ? > > > > > > Laurent Destailleur (aka eldy) > > > > _______________________________________________ > Dolibarr-dev mailing list > Dolibarr-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > >
_______________________________________________ Dolibarr-dev mailing list Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
