[17.0][mig]stock_account_move_reset_to_draft #1854
Conversation
leemannd
changed the title
Corrected inaccurate information in the README.
leemannd
force-pushed
the
17.0-mig-stock_account_move_reset_to_draft
branch
from
921bb40
to
29d3d73
Compare
leemannd
force-pushed
the
17.0-mig-stock_account_move_reset_to_draft
branch
4 times, most recently
from
cadb60a
to
6e1e2f2
Compare
| @@ -4,7 +4,7 @@ | |||
| "name": "Stock account move reset to draft", | |||
| "author": "Tecnativa, Odoo Community Association (OCA)", | |||
| "website": "https://github.com/OCA/account-invoicing", | |||
| "version": "16.0.1.0.1", | |||
| "version": "17.0.1.0.1", | |||
There was a problem hiding this comment.
Some maintainers want to maintain the 3 last version numbers inbetween odoo versions.
I can update it to 17.0.1.0.0 if required
There was a problem hiding this comment.
I thought we were supposed to make it 17.0.1.0.0. What is the rationale of keeping the last three digits?
There was a problem hiding this comment.
Some maintainers keep the 3 digits up to date inbetween versions. The rationale behind this is to be able to know which fixes/features are included.
The usual procedure is to set as you say 17.0.1.0.0.
Beside that @yostashiro , if you have the time for a review, you're welcome.
There was a problem hiding this comment.
That's not the rule, and it shouldn't be, as it's very easy to desynchronize such versions and a maintenance burden to synchronize them with no added benefit. Anyway, the only I know doing it is mis_builder, which is more a Python engine than Odoo code, and then it's more possible (although I also don't like it).
There was a problem hiding this comment.
@pedrobaeza Agreed. I have updated the version number. If you have time to drop a review, you're welcome.
leemannd
force-pushed
the
17.0-mig-stock_account_move_reset_to_draft
branch
from
6e1e2f2
to
6414f82
Compare
|
/ocabot migration stock_account_move_reset_to_draft |
There was a problem hiding this comment.
It seems OK looking at the diff review, but @yostashiro should confirm all the valuation stuff.
Standard migration of the module to 17.0