Contributors

Hi,

With some limitations it is possible to use github actions for older versions. Check the 9.0 branch of the Dutch localization: https://github.com/OCA/l10n-netherlands/tree/9.0. The move from .travis to .github actions is in the last 4 commits.

Kind regards, Ronald

I cringe a bit at the idea of removing automated testing. Is there some reason that it doesn't make sense to migrate these old versions to runboat or some other build tool? If it is a matter of cost, "GitHub Actions usage is free for standard GitHub-hosted runners in public repositories" [1].

[1] https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions

On Sun, Feb 4, 2024 at 5:59 AM Tom Blauwendraat <notifications@odoo-community.org> wrote:

Nice progress, Stephane!

This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:

--> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)

Should we:

A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos

B. Refuse complex PR's; manually merge in smaller or bugfix PR's

C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews

D. Any of the above, as agreed as a policy between the PSC's of the particular repo

I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?

-Tom

On 2/3/24 11:22, Stéphane Bidoul wrote:

Hi everyone,

As previously announced we have cancelled the OCA Travis subscription.

This means Travis CI tests will stop working in OCA repos mid February.

Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

Best regards,

-Stéphane

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Nice progress, Stephane!

This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:

--> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)

Should we:

A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos

B. Refuse complex PR's; manually merge in smaller or bugfix PR's

C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews

D. Any of the above, as agreed as a policy between the PSC's of the particular repo

I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?

-Tom

On 2/3/24 11:22, Stéphane Bidoul wrote:

Hi everyone,

As previously announced we have cancelled the OCA Travis subscription.

This means Travis CI tests will stop working in OCA repos mid February.

Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

Best regards,

-Stéphane

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Nice progress, Stephane!

This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:

--> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)

Should we:

A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos

B. Refuse complex PR's; manually merge in smaller or bugfix PR's

C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews

D. Any of the above, as agreed as a policy between the PSC's of the particular repo

I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?

-Tom

Hi everyone,

As previously announced we have cancelled the OCA Travis subscription.

This means Travis CI tests will stop working in OCA repos mid February.

Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

Best regards,

-Stéphane

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe