|
Hey Greats,
It all happened due to the fact I could not allot time to see the merge. Had I approved, would be no noise at all. Give me few hours, I will check it. IMHO, based on the risk factor of the merge proposal, we should think of time for delay. Thanks. On Thursday 13 June 2013 02:56 PM, Nicolas Bessi wrote: Hello, Error is human. I agree we should wait a minimum time before committing in order to have an optimal number of review. (Emergency case excepted like critical security flow or server crashing error).Having three review on the same MP can be quite difficult the reviewer number is not that big, but at midterm it seems to be a reasonable value, I'm OK with that. For normal complexity fix 5 day seems hard to be sustainable in term of business. I will suggest three working days. Regards Nicolas Le Thu Jun 13 11:10:57 2013, Stefan Rijnhart a écrit :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 I would like to suggest to wait at least five calendar days unless there are three approvals. Please share your opinions. Cheers, Stefan. --
Thanks, Regards,  Serpent Consulting Services. Web : http://www.serpentcs.com Twitter: jaynvora, husendaudi Skype: jaynvora, husen.daudi Blog : http://www.serpentcs.com/blog |
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
