Re: [Dolibarr-dev] Dolibarr 3.7 freeze

[Doursenaud , Raphaël]

Agreed that testing on an ERP is no easy feat.

But I support the idea of a public RC. Advertised efficiently, it would be a good way to get users into the pool.

After all an RC is supposed to be stable, it's what we want to release. It has already passed the beta stages and we consider this should be the final product so it shouldn't have any major defect.

Ideally consecutive betas and RCs should be published at a fixed rate, eg. once a week so there is enough time between each to make some work.

Also, when done correctly, the final release _is_ the last RC.

Cheers,

2014-11-05 0:40 GMT+01:00 Jacques PYRAT <address@hidden>:

address@hidden a écrit le 05/11/2014 00:13 :

The establishment on an "visible" RC version (in the .fr and .org website) will permit users (not necessarily developer) to test more in depth version of this qualification and return faults detected. This is probably also to us to "educate" our clients to back the bugs. everyone will win.

Hi,

I'm an end user of Dolibar.
I'm here because I contribute to an other Open source Project (SPIP)
And so, I use to read developpers discussion to anticipate future.

With SPIP, testing RC is OK.
But with Dolibarr, testing is dangerous !
I don't think that any en user would be confident testing RC given the risk to loose essential data !

My 2 cents,

--
Jacques — www.pyrat.net

_______________________________________________
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

+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