openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #03659
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
Ana,
There are no change in the way we manage stable branches. The only changes are in the way we manage the trunk branch.
As you use the stable branch, nothing change for you. The only visible difference is that v8 will be much stable the day we will release it.
On 27 Oct 2013, at 22:32, Ana Juaristi <ajuaristio@xxxxxxxxx> wrote:
> I'm trying to understand how is it going to work on future but I can not yet.
> Is there any place, slides or documentation about it?
> Some of my concerns and doubts would be:
> - new functionality will be included on stable version each month?
> - there could be db changes on existing modules to make it compatible with that new functionality?
> - if yes.. Would be necesary migrating production data of our customers each month even if we could do it with enterprise contract?
> - how would be avoided regressions?
> - how does this work with localizations and fiscal changes on each country?
> - how does this work with not saas customers having custom modules? Is there any recomendation or methodology for this kind of projects?
>
> Thak you in advance:
> Ana
>
> El 27/10/2013 21:59, "Fabien Pinckaers" <fp@xxxxxxxxxxx> escribió:
>
> > As per slide 28 of http://www.slideshare.net/openobject/openerp-2012-openerp-strategy, the same was supposed to be true for the 7.0 release.
>
> Yes, we wanted to put the saas on trunk before v7 but we did not succeed.
>
> We put a lot of efforts testing an bugfixing v7 before launch, but we did not have any real users in production before the launch. Some bugs are very difficult to find by manual test teams and, unfortunatelly, are detected post launch when going in production.
>
> So, It took us 9 months more to succeed putting saas on trunk. But now, we succeeded; our own instance, all training sessions and saas users are on trunk. And we already did upgrades of the saas without big issues.
>
> One should check stats, but I would say that even more bugs are reported and fixed on trunk than on stable. That's completly new and it's a very good sign for the transition to v8 that will be smoother.
>
>
> > Much as we love OpenERP and appreciate that you put a lot of effort into development and maintenance, we did not experience the 7.0 release as stable (and I am not talking about the partner model, but simply the usability of the core modules).
>
> I know we had lots of issues at the time of the release of v7.
>
> You will probably disagree but overall, compared to the HUGE volume of improvements done in v7, it's not that much. It's even very low compared to v6, v6.1
>
> E.g. We complety replaced the good-old GTK by the web client and we had nearly no issue on the web client. It's a huge piece of code and it's damn stable since its release.
>
> Our ratio "# bugs / volume of changes-improvements" is very low. (*)
>
> Compare this to the number of bugs you introduced with your 60 commits on OCB branch :)
>
>
> (*) but it's not good enough, we must do much better.
>
> > Is it really going to be different this time?
>
> I hope... it's very difficult to predict.
>
> It's a huge challenge to bring in so much improvements, while keeping a strong level of maturity.
>
>
> But now, the risk is not anymore on new releases. V8 will be clean the day we will release it as we will already have thousands users using it for months.
>
> The risk is on our own instance and saas customers for each monthly upgrades.
>
> The challenge is huge (monthly upgrades of saas customers on trunk) but I am very confident. For now on, we do our own production server before saas customers to check everything is clean.
>
> For now on, it's a success but we did not merge yet huge feature branches like the new WMS.
>
>
> >
> > Cheers,
> > Stefan.
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openerp-community
> > Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openerp-community
> > More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
Follow ups
References
-
Proposal to improve communication and make more efficient the inclusion of new branches.
From: Nhomar Hernández, 2013-10-22
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Quentin THEURET, 2013-10-23
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-24
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ronald Portier, 2013-10-24
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Olivier Dony, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Lionel Sausin, de la part de l'équipe informatique Numérigraphe, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Mario Arias, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Olivier Dony, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ferdinand, 2013-10-26
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ferdinand, 2013-10-26
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-27
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan Rijnhart, 2013-10-27
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-27
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ana Juaristi, 2013-10-27