Le 13/07/2012 12:19, Doursenaud, Raphaël a écrit :
Well, planning doesn't mean we should strictly stick to it. It means we have an objective and it gives us visibility.

At least we should be able to announce a tentative date for release. Ask everyone to report problems before. And move the date if too many problems are found.

IMO updated betas should have been numbered, tagged in git and announced publicly. RC cycle could have been a little bit longer and finally last RC must be final release without any modifications. I'd love a collaborative release process where we can all reach consensus on the "it's ready" bit.
We will try to think on how we can validate such a "top". Maybe a doodle survey.


Also, for the feature you ask. It has been added into the 3.2 branch (for 3.2.1 version).
Note sure it works correctly but you can test.
The question that remain is "is such a feature can work ?". I ask this because what happen if the invoice does not contains all content of the order but only first part. The order will be automaticaly modified as "billed". Is this good for you ?


Let me know if I can help.

Cheers,

2012/7/13 Laurent Destailleur (eldy) <[email protected] <mailto:[email protected]>>


    Release was done yesterday, news will appears soon.

    For regression, we discovered it too late. Sorry.
    But this will be fixed into a patch release.


    For roadmap, for the moment, there is only the bug tracker on
    doliforge (project Dolibarr). We try to work on priority 9 first.
    The problem is building a roadmap where features is provided by
    volunteer is difficult to build because we simply don't know which
    feature we will receive...


    Le 13/07/2012 11:58, Doursenaud, Raphaël a écrit :
    Hello developers,

    I just discovered today that 3.2.0 was released. I'm surprised
    there hasn't been any announcement on the mailing list.

    I'm also a bit disappointed because the release contains a major
    regression I have reported a few days ago
    (https://doliforge.org/tracker/?func=detail&group_id=144&aid=444&atid=246).
    If I knew it would be released without a fix, I'd have bugged
    Laurent or Régis about it !

    Do we have a roadmap, a planning or a release process which would
    help external developers to stay in sync with the maintainers
    decisions ?
    If these tools exists, please be kind to me, I've not been able
    to find those despite my searches.
    If not, I think we need some.

    So what do you think ?


--
*Raphaël Doursenaud*
05 35 53 97 13 - 06 68 48 20 10
[email protected] <mailto:[email protected]>


<http://gpcsolutions.fr>
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 EUR - R.C.S. PAU 528 995 921


_______________________________________________
Dolibarr-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev


_______________________________________________
Dolibarr-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

Répondre à