|
| From: | Hubert Andriolo |
| Subject: | Re: [Dolibarr-dev] New rule to report bug and task |
| Date: | Thu, 26 Mar 2015 17:41:08 +0100 |
Send Dolibarr-dev mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dolibarr-dev digest..."
Today's Topics:
1. New rule to report bug and task (Laurent Destailleur (aka Eldy))
2. Re: New rule to report bug and task (Marcos Garc?a)
3. Re: New rule to report bug and task
(Laurent Destailleur (aka Eldy))
4. Re: Transifex for Dolibarr translation can now be used for
all languages (except en_US) (Laurent Destailleur (aka Eldy))
----------------------------------------------------------------------
Message: 1
Date: Thu, 26 Mar 2015 16:08:29 +0100
From: "Laurent Destailleur (aka Eldy)" <address@hidden>
To: ML Dolibarr dev <address@hidden>
Subject: [Dolibarr-dev] New rule to report bug and task
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="utf-8"
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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/f76efa93/attachment.html>
------------------------------
Message: 2
Date: Thu, 26 Mar 2015 16:13:23 +0100
From: Marcos Garc?a <address@hidden>
To: "Posts about Dolibarr ERP & CRM development and coding"
<address@hidden>
Subject: Re: [Dolibarr-dev] New rule to report bug and task
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="utf-8"
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*
address@hidden
2015-03-26 16:08 GMT+01:00 Laurent Destailleur (aka Eldy) <
address@hidden>:
> 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
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/510cdae3/attachment.html>
------------------------------
Message: 3
Date: Thu, 26 Mar 2015 16:26:43 +0100
From: "Laurent Destailleur (aka Eldy)" <address@hidden>
To: "Posts about Dolibarr ERP & CRM development and coding"
<address@hidden>
Subject: Re: [Dolibarr-dev] New rule to report bug and task
Message-ID:
<CALeEO_mK35dELu+v17=-address@hidden>
Content-Type: text/plain; charset="utf-8"
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 <address@hidden>:
> 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*
>
> address@hidden
>
>
> 2015-03-26 16:08 GMT+01:00 Laurent Destailleur (aka Eldy) <
> address@hidden>:
>
>> 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
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
>>
>>
>
> _______________________________________________
> Dolibarr-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/faa1cea1/attachment.html>
------------------------------
Message: 4
Date: Thu, 26 Mar 2015 16:45:29 +0100
From: "Laurent Destailleur (aka Eldy)" <address@hidden>
To: "Posts about Dolibarr ERP & CRM development and coding"
<address@hidden>
Subject: Re: [Dolibarr-dev] Transifex for Dolibarr translation can now
be used for all languages (except en_US)
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="utf-8"
Yes, only english is now maintained with git edition.
All other languages are hosted on transifex and synchronized with script
dev/translations/txpull.sh (it gets translated files and clean langages
files so "alternative" language like es_MX contains only difference with
main language es_ES).
This wil save me a lot of time when preparing a release.
2015-03-16 17:15 GMT+01:00 Doursenaud, Rapha?l <address@hidden>
:
> Great!
>
> Just to be sure, this means that only English US is maintained through the
> repository, right?
>
> Thanks.
>
> 2015-03-16 1:41 GMT+01:00 Laurent Destailleur (aka Eldy) <
> address@hidden>:
>
>> Starting from today, Transifex is not restricted anymore to major
>> languages.
>>
>> All languages, even alternatives languages (like pt_BR, es_MX, es_DO,
>> ...) are now included into the transifex process.
>> Sync is also supported for those languages.
>>
>> Documentation for translator has been updated here:
>> http://wiki.dolibarr.org/index.php/Translator_documentation
>>
>>
>> Laurent, aka Edly.
>>
>> _______________________________________________
>> Dolibarr-dev mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
>>
>>
>
>
> --
> *Rapha?l Doursenaud*
> Directeur technique (CTO)
> Expert certifi? en d?ploiement Google Apps
> <https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist>
> +33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10
>
> <http://gpcsolutions.fr>
> http://gpcsolutions.fr
> Technopole H?lioparc
> 2 avenue du Pr?sident Pierre Angot
> 64053 PAU CEDEX 9
> SARL GPC.solutions au capital de 7 500 ? - R.C.S. PAU 528 995 921
>
> <http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions>
>
> _______________________________________________
> Dolibarr-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/dolibarr-dev/attachments/20150326/60831f9d/attachment.html>
------------------------------
_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
End of Dolibarr-dev Digest, Vol 144, Issue 11
*********************************************
| [Prev in Thread] | Current Thread | [Next in Thread] |