← Back to team overview

openerp-community team mailing list archive

Re: Proposal to improve communication and make more efficient the inclusion of new branches.

 

Oliver,

El oct 28, 2013 12:11 PM, "Olivier Dony" <odo@xxxxxxxxxxx> escribió:
>
> On Mon, Oct 28, 2013 at 8:05 PM, Moises Lopez <moylop260@xxxxxxxxxx>
wrote:
>>
>> Hello Oliver,
>>
>> Current openerp-runbot there is hard-code for sticky branches.
>
> Actually, this can be configured dynamically too. But first the team
config must be clean.

Yes, sorry you are right.
I make changes for add many addons branches and check MP (my particular
needs for l10n_mx sticky).

For ocb with original runbot should be done.

>
>>
>> I modified this file for explain this point:
>>
>>
https://docs.google.com/spreadsheet/ccc?key=0AotaKTc4rOjsdGYyaU5IbHVJbHFkY0thNEVqa2hwckE&usp=sharing
>> Can you see row 9 of this spreadsheet?
>
> Yes I saw the spreadsheet and I had a quick look at your patches to
runbot too, but I don't think we'll want to merge that. We would prefer if
not everyone is allowed to setup sticky branches, as people are very good
at misusing the tools you give them, and the cases where a sticky branch is
needed should be fairly limited.

You're right.
Should be fairly limited, but IMHO no hard code then no openerp-runbot
restart.

Now, the question is:
Will you add ocb branches to sticky (from hard-code)? (later of cleanup)

Have you planned add localization projects in RunBot like sticky?

FYI our runbot was modify for this.
Our small server is available to the community, too.

>

References