Re: [Dolibarr-dev] We need bug fixers, not feature developers !

[Destailleur Laurent]

This report you used is a view "after the war" (after fixing all bugs).

If you take a look of bugs with status "fixed" and reported during 3.5 beta (this view can provide an idea of part of it:

https://doliforge.org/tracker/?atid=246&group_id=144&func=browse&set=custom&advsrch=1&msort=0&report_id=246&submitted_by%5B%5D=0&status_id%5B%5D=0&resolution_id%5B%5D=1&severity%5B%5D=0&assigned_to%5B%5D=0&category_id%5B%5D=0&release_id%5B%5D=105&release_id%5B%5D=117&release_id%5B%5D=119&release_id%5B%5D=118&release_id%5B%5D=111&chunksz=50),

you will see that more than 200 bugs were reported but 95% of them were fixed by only 3 different people (and 80% of fix PR were sent by one developer). This is not real number of bugs during beta. Because a lot of bugs were reported onto forums or ML only and not into tracker. I think we had to fix more than 400 bugs for this version (it is same number than previous versions like 3.4 or 3.3), but what is important to notice is that ratio of different developers workings on fixes is same (80% of fixes are coming from one developer only and 95% of fixes from 3 different developers only). It would be better if we can received more fixing PR from more different developers, above all during beta, so we can balance this ratio differently.

2014-02-24 16:13 GMT+01:00 Marcos García <address@hidden>:

Hi Laurent,

I've checked the page and I only see 7 bugs, 4 of them written in French instead of English. I don't see the problem that big, why do you do?

FYI: https://doliforge.org/tracker/?atid=246&group_id=144&func=browse&set=custom&advsrch=0&msort=0&report_id=246&submitted_by=0&status_id=1&resolution_id=100&severity=0&assigned_to=0&category_id=0&release_id=0&chunksz=50

Regards,

 

Marcos García

address@hidden

2014-02-24 11:59 GMT+01:00 Destailleur Laurent <address@hidden>:

I used a title that may hurt every developer. This is just to be sure everybody read my note ;-)

Dolibarr is now a very large success among a very large number of users but also developers. 

During 3.5 beta and still now, we had received a lot of (too much ?) number of Push request for new feature, but nearly no code to fix bug. 

80% of request coming from external developers was new feature. Each request to add feature introduce around 2 bugs (this is an average value). This means to keep the bug ratio to same level we nee to spend 66% of code change (PR) to fix bug and 33% of code change (PR) to add new features.

Because external submission are 80% of PR (Pull Request) to add new feature, we are far away of this ratio. The only one solution we had to not see the bug rate increase dangerously is to have the core team to work ONLY on bug fixes. 

This is what happened during all the 3.5 period (so several month). But this means also there is less time to validate "major" pull requests of really intersting new features. 

So some of you may see their pull request with status "pending" even several month after submitting them. Sorry for that. And after a long time, i will probably have to discard completely this pull request that can't be merged easily. Sorry 2.

There is now so many people using Dolibarr, that keeping quality and keeping bug rates under control must be a priority, before adding new feature. But this does not mean we will slow down the increase f new feature. This just means that the conclusion is a strange paradox: if you want to help dolibarr project to increase the number of feature, make priority on bugs fix on old feature ! 

(so bug rate will go down and if bug rate goes down, you will see new feature appears more quickly !)...

Does this means Dolibarr popularity is growing too quickly ? May be, but this is a good news, isn't it ?

All this text to finally thanks all guys (core team and others) that helped me to fix bugs during the 3.5 beta ! and just after the release of 3.5. I hope they will understand it is a bug thanks !

PS: Well 3.5.1 will be released very soon with result of all fixes... 

PPS: To find what are opened bugs, just create an account on doliforge.org and go onto this report:

https://doliforge.org/tracker/?atid=246&group_id=144&func=browse

And use the comments of tickets to ask advice on how you can fix a selected bug...

 

 

Laurent, Dolibarr main project leader

------------------------------------------------------------------------------------

Google+: https://plus.google.com/+LaurentDestailleur/

Facebook: https://www.facebook.com/Destailleur.Laurent

Twitter: http://www.twitter.com/eldy10

_______________________________________________
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

--

Laurent Destailleur (alias Eldy)

------------------------------------------------------------------------------------

Social networks of my OpenSource projects:

Dolibarr Google+: https://plus.google.com/+DolibarrOrg/

Dolibarr Facebook: https://www.facebook.com/dolibarr

Dolibarr Twitter: http://www.twitter.com/dolibarr

AWStats Google+: https://plus.google.com/+AWStatsOrgPoject/

AWStats Facebook: https://www.facebook.com/awstats.org

AWStats Twitter: http://www.twitter.com/astats_project