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

[ADD] Logistics: Release Channel, Reservation and Shopfloor repositories #66

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

rousseldenis
Copy link
Contributor

@rousseldenis rousseldenis commented Jan 24, 2025

@OCA/logistics-maintainers

Before first PR's creation in 18.0 repository and because modules amount in that field are quite important, I suggest to create a separate repository for release channel management.

See: https://github.com/OCA/wms

@rousseldenis rousseldenis force-pushed the add-18-release_channel-dro branch from ad47735 to ce96854 Compare January 24, 2025 11:46
@jbaudoux
Copy link
Contributor

What about dropping completely wms and reclassifying into:

  • stock-logistics-shopfloor : shopfloor* modules
  • stock-logistics-reservation : promise stuffs and reserve rule
  • stock-logistics-release-channel : release channel *
  • stock-logistics-workflow : dyn routing, batch creation, storage type, warehouse flow
  • delivery-carrier : delivery_carrier_warehouse (already merged, I was too quick..)

@sebalix
Copy link
Contributor

sebalix commented Jan 24, 2025

Good idea from @jbaudoux, it's a bit difficult to guess if a logistic module should land in wms or stock-logistics-* repo.

@rousseldenis
Copy link
Contributor Author

What about dropping completely wms and reclassifying into:

  • stock-logistics-shopfloor : shopfloor* modules
  • stock-logistics-reservation : promise stuffs and reserve rule
  • stock-logistics-release-channel : release channel *
  • stock-logistics-workflow : dyn routing, batch creation, storage type, warehouse flow
  • delivery-carrier : delivery_carrier_warehouse (already merged, I was too quick..)

I can add shopfloor and reservation repos here.

@hparfr
Copy link

hparfr commented Jan 24, 2025

stock_logistics_delivery_carrier to be consistent

@rousseldenis
Copy link
Contributor Author

stock_logistics_delivery_carrier

No, no. We use existing delivery-carrier repo.

@rousseldenis rousseldenis changed the title [ADD] Release Channels repository [ADD] Logistics: Release Channel, Reservation and Shopfloor repositories Jan 24, 2025
@simahawk
Copy link
Contributor

The idea behind "WMS" was to have meaningful name for a WMS solution.
What I suggest: we could move around the specific modules and keep or create in WMS only modules that provide a bundle of feature for specific WMS cases.

@rousseldenis
Copy link
Contributor Author

The idea behind "WMS" was to have meaningful name for a WMS solution. What I suggest: we could move around the specific modules and keep or create in WMS only modules that provide a bundle of feature for specific WMS cases.

Yes, in fact, WMS is more a "verticalization" as this should point to useful modules to do a complete WMS solution.

Maybe, this repo could become something more functional.

@simahawk
Copy link
Contributor

Regarding shopfloor: the base modules should be moved to its own repo like shopfloor or shopfloor-app, because it can be used for apps that do not belong to logistics.

@rousseldenis
Copy link
Contributor Author

Regarding shopfloor: the base modules should be moved to its own repo like shopfloor or shopfloor-app, because it can be used for apps that do not belong to logistics.

Agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants