You probably don't know, but board team planned to upgrade Tuleap one year ago ! First try were done during last year dev camp. And we experience too much problem and had to restore our VM.
We also contact the Tuleap team to make migration for us. They agree but one year after we are still in our old version. So I decided that 1 year waiting trying to have a better tracker, with no result, was enough and foundation board voted to migrate to something else (4 vote for, 2 no vote and one vote against). Github was just the solution "ready". 2015-03-26 16:13 GMT+01:00 Marcos García <[email protected]>: > Wouldn't updating the old Tuleap to the last version fix most of the > problems? > > Closing issues through commits is easy to manage with Github hooks. > > I tell you this because Github's issues are not as powerful as having a > professional bug tracker. > > Regards, > > > *Marcos García* > > [email protected] > > > 2015-03-26 16:08 GMT+01:00 Laurent Destailleur (aka Eldy) < > [email protected]>: > >> 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 >> [email protected] >> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev >> >> > > _______________________________________________ > Dolibarr-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > >
_______________________________________________ Dolibarr-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
