Tools mailing list archives

tools@odoo-community.org

Avatar

Re: Maintainer-Tools v9

by
ClosingAp Open Source Integrators Europe, LDA, Daniel Reis
- 27/08/2016 16:15:39
I think the majority of the content does not benefit from branches, and it would even make it confusing.

I'm :-1: for adding branches.

Alternatives suggested:

a) move templates to MQT repo (that needs branches by now)
b) create specific repo for that (not my preferred choice, since that could make them harder to be found)

--
Daniel

No dia 24/08/2016, às 16:53, Dave Lasley <dave@laslabs.com> escreveu:

Did anyone else have any thoughts on the matter?


On Aug 18, 2016, at 9:07 AM, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

For me it's clearly +1 to have branches for different versions.

Regards.

P.S.: Dave, your mails always appear as spam because it says that your address is not verified by laslabs.com.

2016-08-18 16:23 GMT+02:00 Dave Lasley <dave@laslabs.com>:

Hi All,


I would like to propose that we branch maintainer-tools the same way we do Odoo, providing a branch for each version.

My reasoning behind this is that the template module is becoming a pseudo-documentation, which is being limited by the fragmentation of APIs.

For current examples PRs upgrading to v9, please see:

_______________________________________________
Mailing-List: http://odoo-community.org/groups/tools-22
Post to: mailto:tools@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe



_______________________________________________
Mailing-List: http://odoo-community.org/groups/tools-22
Post to: mailto:tools@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe



_______________________________________________
Mailing-List: http://odoo-community.org/groups/tools-22
Post to: mailto:tools@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

<signature.asc>
<Symbol_small.png>

Reference