Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MIG][16.0] product_packaging_type_pallet => product_packaging_level_pallet #1216

Closed

Conversation

@rousseldenis
Copy link
Sponsor Contributor Author

/ocabot migration product_packaging_type_pallet

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Nov 29, 2022
@OCA-git-bot OCA-git-bot mentioned this pull request Nov 29, 2022
55 tasks
@rousseldenis rousseldenis reopened this Nov 29, 2022

|badge1| |badge2| |badge3| |badge4| |badge5|

This module adds specific fields to manage product packaging types for pallets.
Copy link
Sponsor Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This module adds specific fields to manage product packaging types for pallets.
This module adds specific fields to manage product packaging levels for pallets.

Copy link
Contributor

@jbaudoux jbaudoux Mar 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, don't change this, it is a package type specialization, not a package level

# Copyright 2019 Camptocamp SA
# License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl)
{
"name": "Product Packaging Type Pallet",
Copy link
Sponsor Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"name": "Product Packaging Type Pallet",
"name": "Product Packaging Level Pallet",

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, don't change this, it is a package type specialization, not a package level

# License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl)
{
"name": "Product Packaging Type Pallet",
"summary": "Manage packaging of pallet type",
Copy link
Sponsor Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"summary": "Manage packaging of pallet type",
"summary": "Manage packaging level of pallet",

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, don't change this, it is a package type specialization, not a package level

@@ -0,0 +1,29 @@
# Project C2C Migration information
Copy link
Sponsor Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file should be removed

Copy link
Member

@FrancoMaxime FrancoMaxime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @lmignon comments

Copy link
Contributor

@jbaudoux jbaudoux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that we have package level and package types, this needs to be migrated to the right logistic concept.

It is a packaging type that can be marked as a pallet.
It doesn't make sense to mark a package level as a pallet. A pallet is a tertiary level. There is always one and only one tertiary level. However, you can have multiple package type on a tertiary level and some can be marked as pallet.

Rename the module, and remove the dependency on product_packaging_level. Set is_pallet on package type instead.

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 30, 2023
@bealdav
Copy link
Member

bealdav commented Aug 17, 2023

Hi, thanks for this contribution.
I don't if this PR 'll be achieved considering @jbaudoux comment.

On my side, regarding the python code I don't know why this module depends on product_packaging_dimension. None of the python code is related to this module. Probably only because of the xml view.

To guess what is a pallet, I suppose that level can be used without this module (convention by project ?)

Do you what'll become this PR ? Thanks

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 20, 2023
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Dec 24, 2023
@hspl-priva
Copy link

LGTM @rousseldenis @pedrobaeza tested. it seems good. any idea when can we merge this?

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jan 21, 2024
@simahawk
Copy link
Contributor

@rousseldenis ping

Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 16, 2024
@github-actions github-actions bot closed this Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration needs review stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.