Re: [Dolibarr-dev] Again, released new version without any notification

[Doursenaud , Raphaël]

2014-03-12 19:34 GMT+01:00 Destailleur Laurent <address@hidden>:

The release process is a process that takes a lot of work and need a lot of talks. It is not possible to do all this talks on one minutes, all at same time. That why notification may be sent few days after release, tests that all sync with mirrors are ok and that packages are ok.

Hi Laurent,

I think you're missing that there are two different problems here :

- developper/translators/community announcement

- public/global annoncement

Making the first announcement would warn everyone involved in the community that a realease is about to happen.

This way Marcos would not have been surprised by an end user and would have had the perfect answer : "The release is not _yet_ official, please wait and refer him to the release process rules" and Saxa would have known he needed to hurry for it's change to be integrated in the next release.

Your view is valid for the second case, for which I completely agree with you :

It should only be done once we're sure everything went smoothly but you can't prevent people from monitoring sourceforge.

Anyway, our process is far from perfect and needs some love.

I'm ready to help as much as I can but the way I work, I prefer to raise a consensus before doing any work hence my call for comments on the wiki. (BTW it's missing talk pages that are usefull for this kind of work.)

Cheers,
--

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

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