- Mailing Lists
- Contributors
- Porting a module from the OCA whose feature is now in Odoo CE
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
Porting a module from the OCA whose feature is now in Odoo CE
The functionality of module stock_picking_responsible in v12 is now part of Odoo CE in v16 but it still needs a migration script* : what should I do in this case ?
My intuition is to port stock_picking_responsible to v16 and only leave the migration script in the module. I'm afraid this would clutter the oca repository with empty repositories.
What do you people think ?
All the best,
* more detail :
responsible_id is a many2one to a res.partner in stock_picking_responsible
responsible_id is a many2one to a res.users in stock
by Robin Keunen - 07:01 - 21 Nov 2023
Follow-Ups
-
Re: [SPAM] Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
Hi Pedro,
I did not get your suggestion either, I’ll move it to open upgrade as you suggest, thanks !
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40On 22 Nov 2023, 16:04 +0100, Francesco Foresti <notifications@odoo-community.org>, wrote:
@Pedro I didn't receive the email as well. Sometimes newsletter skips some replies (maybe even questions?) and that's not really ideal as there's no feedback on that...Maybe it could be a good reason to switch to https://github.com/orgs/OCA/discussions ? Not to hijack this thread :)
Cheers
Il giorno mer 22 nov 2023 alle ore 15:47 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:Did you receive my mail stating the regular procedure?> Add the merge of the module in OpenUpgrade, and include the migration script there.> Example: https://github.com/OCA/OpenUpgrade/pull/4191Regards._______________________________________________
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
by Robin Keunen - 04:25 - 22 Nov 2023 -
Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
@Pedro I didn't receive the email as well. Sometimes newsletter skips some replies (maybe even questions?) and that's not really ideal as there's no feedback on that...Maybe it could be a good reason to switch to https://github.com/orgs/OCA/discussions ? Not to hijack this thread :)
CheersIl giorno mer 22 nov 2023 alle ore 15:47 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:Did you receive my mail stating the regular procedure?> Add the merge of the module in OpenUpgrade, and include the migration script there.> Example: https://github.com/OCA/OpenUpgrade/pull/4191Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Francesco Foresti - 04:04 - 22 Nov 2023 -
Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
Did you receive my mail stating the regular procedure?> Add the merge of the module in OpenUpgrade, and include the migration script there.> Example: https://github.com/OCA/OpenUpgrade/pull/4191Regards.
by Pedro M. Baeza - 03:45 - 22 Nov 2023 -
Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
Thanks for the suggestion. I ended up doing that but for version 13 (PR) since the Responsible field was introduced in that version.
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40On 21 Nov 2023, 23:12 +0100, Adam Heinz <notifications@odoo-community.org>, wrote:
It certainly seems to me that you'll need a migration script to reshape the data from OCA v15 into Odoo CE v16. I don't see how that would contribute to clutter as the module could simply never exist for OCA v17+.
On Tue, Nov 21, 2023 at 1:02 PM Robin Keunen <notifications@odoo-community.org> wrote:Hi community,
The functionality of module stock_picking_responsible in v12 is now part of Odoo CE in v16 but it still needs a migration script* : what should I do in this case ?
My intuition is to port stock_picking_responsible to v16 and only leave the migration script in the module. I'm afraid this would clutter the oca repository with empty repositories.
What do you people think ?
All the best,
* more detail :
responsible_id is a many2one to a res.partner in stock_picking_responsible
responsible_id is a many2one to a res.users in stock
_______________________________________________
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
by Robin Keunen - 03:35 - 22 Nov 2023 -
Re: Porting a module from the OCA whose feature is now in Odoo CE
It certainly seems to me that you'll need a migration script to reshape the data from OCA v15 into Odoo CE v16. I don't see how that would contribute to clutter as the module could simply never exist for OCA v17+.On Tue, Nov 21, 2023 at 1:02 PM Robin Keunen <notifications@odoo-community.org> wrote:Hi community,
The functionality of module stock_picking_responsible in v12 is now part of Odoo CE in v16 but it still needs a migration script* : what should I do in this case ?
My intuition is to port stock_picking_responsible to v16 and only leave the migration script in the module. I'm afraid this would clutter the oca repository with empty repositories.
What do you people think ?
All the best,
* more detail :
responsible_id is a many2one to a res.partner in stock_picking_responsible
responsible_id is a many2one to a res.users in stock
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Adam Heinz - 11:10 - 21 Nov 2023