Same thing, automate. Unit tests and functional tests FTW.
Granted it takes some time to write but the effort is worth it ans it's a sane habit to have. Check out the module template I maintain for a starting point : https://github.com/Dolibarr/dolibarr-module-template Yes, I have a blog post in the works about that but I'm too busy with paying jobs at the moment. Le 19 oct. 2016 4:50 PM, "Charles Benke" <charles...@benke.fr> a écrit : > Actually I maintain 22 modules, some are simple, some are complex. To test > all of them correctly (use all feature, modify doc, …) each time a new > major version of Dolibarr is release is more than 2 full weeks long for > Romain an me... > > During the month a new version comes out, sales of modules on dolistore > are halved cut (according to my information it is not related to my modules > only). > > > > I could do as some others … , just change the version number and wait for > my clients put bugs me but I do not find it honest > > > > Most integrators with whom I work no longer wish to upgrade versions as > there are no major advances between two versions either-called major > > The final version of each major costs money and energy to NOTHING: just to > show that development teams are able to release two versions per year, two > versions full of vacuum . > > > > We have all been waiting for new accountancy module for 2 years. The time > spent to release a new version will have better been employed to work on > this strategic module… > > > > > > Bien cordialement, > > Charlie Benke > > > > *De :* Dolibarr-dev [mailto:dolibarr-dev-bounces+charles.fr= > benke...@nongnu.org] *De la part de* Developpement | Open-DSI > *Envoyé :* mercredi 19 octobre 2016 16:24 > *À :* Posts about Dolibarr ERP & CRM development and coding < > dolibarr-dev@nongnu.org> > *Cc :* dolibarr-associat...@nongnu.org > *Objet :* Re: [Dolibarr-dev] [Dolibarr-association] Dolibarr 4.0.1 > > > > Hi > > Thanks to Camille for pointing the main problem : Module and ratio time > spend / bug / patch > As integrator of Dolibarr, it's not "sustainable" for me to test every six > month Dolibarr and the modules I'm commonly using. Today I only install > 3.9. Maybe next year, I will uprade to 5.0 or not... depending of what > functions will be added or remaining experimental. > Modules are too often broken by new version. On the Dolistore you can see > module labeled 3.x-4.0 who are in fact broken with the last version or > doesn't exist for the current version of Dolibarr. I think it's not good > for the reputation of Dolibarr. > I'll be pleased to discuss about this subject in Valence :-) > > Regards > Philippe Scoffoni - Open-DSI > > > Le 19/10/2016 à 15:14, cam.la...@azerttyu.net a écrit : > > Hi > > > > Thanks for sharing this. > > I agree, Dolibarr migration is pretty nice ! > > > > but only core part, modules looks more problematic to update. > > > > Regarding communication, this is a work in progress. > > > > Yes I saw this :) But looks again difficult. But it's better :) > > > > From now on, we'll have systematic annoucement when a major version is > released, minor version too, why not. A communication group has been > started within the fundation with the goal to better communicate with the > community. We already are present on social medias, but this dev > mailing-list and the dolistore customers are 2 audiences we poorly > communicate with (not to say not at all). > > > > I don't understand logic, dolibarr users/community are on forum, > mailinglist but piority is social network, strange > > > > About your concerns around PRs and plugins, I'm sorry you feel that way. > PRs are usually correctly integrated and not lost. > > > > Maybe now, I'll try again. But I'm not sure. My fear is to lost again > energy to nothing. > > > > Plugins are the responsibility of their developers. Personnaly, our > plugins are upgraded with the new releases > > > > I'm not module developper then I don't know if is complicate or not to > follow release and provide. As user, i prefer to have my own script and > don't use module. In my use case ratio time spend / bug / patch is too > heavy. > > Thanks a lot > > > > km > > > > > _______________________________________________ > > 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 > > -- <https://gpcsolutions.fr> https://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 Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
