openerp-community team mailing list archive

[Nhomar Hernández <nhomar@xxxxxxxxx>]

I am not agreed at all.

5 days per merge can delay so much the deploy in our local releases.

IMHO 2 approvals maybe 3? no matter the time is enought.

We develop, mantain and test everything eith the same branches even we don
put in production if we have pending a community merge proposal.

If somebody ask explicitally for a bigger delay for a fundamented reason it
can be delayed (just specific cases)

Regards.



Written from my android
On Jun 13, 2013 4:41 AM, "Stefan Rijnhart" <stefan@xxxxxxxx> wrote:

> Hi,
>
> apparently we need to establish a concensus on a very concrete number of
> days before a proposal can be merged on projects that have joint the
> community review. See the discussion here: https://code.launchpad.net/~**
> vauxoo/server-env-tools/7.0-**added_o2m_handling-dev-**
> sabrina/+merge/169103<https://code.launchpad.net/~vauxoo/server-env-tools/7.0-added_o2m_handling-dev-sabrina/+merge/169103>
>
> I would like to suggest to wait at least five calendar days unless there
> are three approvals. Please share your opinions.
>
> Cheers,
> Stefan.
>
> --
> Therp - Maatwerk in open ontwikkeling
>
> Stefan Rijnhart - Ontwerp en implementatie
>
> mail: stefan@xxxxxxxx
> tel: +31 (0) 614478606
> http://therp.nl
> https://twitter.com/therp_**stefan <https://twitter.com/therp_stefan>
>
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**openerp-community<https://launchpad.net/~openerp-community>
> Post to     : openerp-community@lists.**launchpad.net<openerp-community@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~**openerp-community<https://launchpad.net/~openerp-community>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>