- Mailing Lists
- Contributors
- New check for the development_status manifest key
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
New check for the development_status manifest key
Dear contributors,
A new validity check for the development_status manifest key has been enabled on all branches.
As a reminder, the valid values are 'Alpha', 'Beta', 'Production/Stable', 'Mature' and the default is 'Beta'. You can read more about the meaning of these values at https://odoo-community.org/page/development-status.
This check is part of pylint-odoo (thanks Moises!)
Up to 12, this is done as part of the lint step of OCA/maintainer-quality-tools.
From 13, this is part of the pre-commit checks.
This check must pass to get a green build on all branches, because invalid values cause issues down the line. In particular, invalid development status keys prevent publication to https://odoo-community.org/apps.
Best regards,
-sbi
by Stéphane Bidoul - 09:11 - 4 Nov 2020
Follow-Ups
-
Re: New check for the development_status manifest key
Great, thanks for the update!On Wed, Nov 4, 2020 at 9:12 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Dear contributors,A new validity check for the development_status manifest key has been enabled on all branches.As a reminder, the valid values are 'Alpha', 'Beta', 'Production/Stable', 'Mature' and the default is 'Beta'. You can read more about the meaning of these values at https://odoo-community.org/page/development-status.This check is part of pylint-odoo (thanks Moises!)Up to 12, this is done as part of the lint step of OCA/maintainer-quality-tools.From 13, this is part of the pre-commit checks.This check must pass to get a green build on all branches, because invalid values cause issues down the line. In particular, invalid development status keys prevent publication to https://odoo-community.org/apps.Best regards,-sbi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, Freelance in love with open source.
by Simone Orsi - 11:15 - 4 Nov 2020