|
From: | Charles Benke |
Subject: | Re: [Dolibarr-dev] Dolibarr 3.8.1 and freeze of Dolibarr 3.9 |
Date: | Wed, 14 Oct 2015 18:59:48 +0200 |
You're right about the various hearings but what is that to focus first? The developers can take a scratch version github Users on sourceforge the latest version dated (even if the version number is smaller ...) once again it does not answer the right question: how to ensure that new users use the most stable version possible Quality code is part of the response, the schedule is another Bien cordialement, Charlie Benke De : address@hidden [mailto:address@hidden De la part de Doursenaud, Raphaël Ok, who's up for a software lifecycle and version numbering schemes thesis? Maybe you can get a PhD out of it! Jokes aside, the thing is that NO software release cycle is perfect because various audiences seek different things. FLOSS developers tend to prefer "release often, release early" and "semantic versioning". Perfectionists are going for "when it's ready" and "I only need to increase one number since every release is just perfect". Traditional corporate vendors usually prefer "Rush it out the door, we need it for yesterday, just try to hide defects under the carpet and colorful design" and "We don't care, give us the biggest number so marketing can show off". Integrators and users want "Something with all the bells and whistles that works out of the box, forever" and "No new releases, they are a pain to deploy, so give me all the features in this one". To which I reply: "Not gonna happen!". The current process is designed around the need to get code out at a regular pace with some predictability to it. It gives a version (N-2) supported roughly 1 and a half year. I don't think it's that great, but at least it's there! IMO The Dolibarr project's lifecyle is missing some key elements to achieve better releases quality before even thinking about changing the release periodicity or version numbering. Here's a non exhaustive list from the top of my head:
As you can see, there's a lot of work and it can't be done by any single individual. The whole community needs to get involved. But for that to happen, there should be a strong commitment from the maintainers and core developers to stick to it and make it happen. We've already made some good progresses since switching to GitHub. Code is reviewed more often and bug reports are all assessed and properly tagged (I devote some of my own time to that weekly). Keep in mind that all of that is a community effort, so the best thing to do is step up to the plate, pick a task and do something ;) Looking forward to your contributions! 2015-10-14 8:23 GMT+02:00 Jean-François Ferry <address@hidden>:
-- Raphaël Doursenaud Directeur technique (CTO) Expert certifié en déploiement Google Apps +33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10 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 |
[Prev in Thread] | Current Thread | [Next in Thread] |