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

[14.0][MIG] account_fiscal_year #1081

Merged
merged 26 commits into from
Jan 29, 2021

Conversation

SimoRubi
Copy link
Member

@SimoRubi SimoRubi commented Nov 6, 2020

Migration extracting from v13 core, based on #1069 (comment)

damdam-s and others added 24 commits November 5, 2020 17:10
* Add contributors to README
* try to find a FY start date according to the start date from choosen period
* Unable to unlink a date_range with type fiscal_year
* `fiscal_year` flag readonly
* add menu to date_range under accounting section
* remove method on  object because it's the same as in  file
* unable to delete  with flag 'fiscal_year' but can delete
* clean __openerp__.py
* account_fiscal_year version number
[MIG] Migrated module 'account_fiscal_year' to V10
[UPD] Update account_fiscal_year.pot
Update translation files

Updated by Update PO files to match POT (msgmerge) hook in Weblate.
This date.range.type in v11 have benn used in some cases. Then, when you migrate, you need to have this data or else delete its xmlid.

We think it's better to keep it, because you may want to still use it.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: account-financial-tools-12.0/account-financial-tools-12.0-account_fiscal_year
Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-12-0/account-financial-tools-12-0-account_fiscal_year/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: account-financial-tools-13.0/account-financial-tools-13.0-account_fiscal_year
Translate-URL: https://translation.odoo-community.org/projects/account-financial-tools-13-0/account-financial-tools-13-0-account_fiscal_year/
@OCA-git-bot
Copy link
Contributor

Hi @eLBati,
some modules you are maintaining are being modified, check this out!

@SimoRubi SimoRubi marked this pull request as ready for review November 6, 2020 12:04
@luc-demeyer
Copy link
Contributor

I don't think we need to have a depends on date_range for this module.

@SimoRubi
Copy link
Member Author

SimoRubi commented Nov 6, 2020

I don't think we need to have a depends on date_range for this module.

Thanks @luc-demeyer for having a look!
I checked and the date range type has been explicitly added by 9b4da88 and looks like there are some reasons to have it.
I'd keep it here because as for what concerns the migration, I'd try not to insert/remove any previous behavior.

I have just now remembered to update the README so I also mentioned it in there.

@luc-demeyer
Copy link
Contributor

@SimoRubi @MiquelRForgeFlow
I looked at 9b4da88 and still don't see a valid reason to keep the date_range dependency.
We may add a migration script to migrate the "fiscal_year" date_range objects to the account_fiscal_year objects but this can be done via post-migrate SQL script.

Copy link
Contributor

@MiquelRForgeFlow MiquelRForgeFlow left a comment

Choose a reason for hiding this comment

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

In this case, migration scripts are not needed. It's fine.

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

Copy link
Member

@tafaRU tafaRU left a comment

Choose a reason for hiding this comment

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

Some nitpicking and questions, but looks good overall. Thanks a lot!

account_fiscal_year/__manifest__.py Show resolved Hide resolved
account_fiscal_year/models/res_company.py Outdated Show resolved Hide resolved
account_fiscal_year/models/res_company.py Show resolved Hide resolved
@AaronHForgeFlow
Copy link
Contributor

In this case, migration scripts are not needed. It's fine.

why? shouldn't we migrate from date_ranges to fiscal years?

@tafaRU
Copy link
Member

tafaRU commented Jan 22, 2021

@AaronHForgeFlow, are you ok with the merge even though #1081 (comment)?

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@tafaRU
Copy link
Member

tafaRU commented Jan 29, 2021

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 14.0-ocabot-merge-pr-1081-by-tafaRU-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit b601250 into OCA:14.0 Jan 29, 2021
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at b0f1d18. Thanks a lot for contributing to OCA. ❤️

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

Successfully merging this pull request may close these issues.