[18.0][MIG] hr_payroll_period: migrate to 18.0 #184
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
dreispt
commented
Jan 26, 2025
dreispt
commented
- [14.0] [ADD] hr_payroll_period
- [MIG] hr_payroll_period: migration to 15.0
- [FIX] hr_perioll_period: fields definition
- Translated using Weblate (Spanish)
- [IMP] hr_payroll_period: Add a cron to create next fiscal year automatically
- [MIG] hr_payroll_period: Migration to 16.0
- [UPD] Update hr_payroll_period.pot
- [BOT] post-merge updates
- [IMP] hr_payroll_period: pre-commit execution
- [MIG] hr_payroll_period: Migration to 18.0
- [MIG] payroll,hr_payroll_period: changes from migration to 17.0
- [MIG] hr_payroll_period: migration to 17.0
[14.0] [ADD] hr_payroll_period: Add mantainers key [14.0] [ADD] hr_payroll_period: Change manifest category [14.0] [ADD] hr_payroll_period [14.0] [ADD] hr_payroll_period [14.0] [IMP] hr_payroll_period: Improve views [14.0] [IMP] hr_payroll_period: Improve views and misc [14.0] [IMP] hr_payroll_period: Improve views and misc [14.0] [IMP] hr_payroll_period: Improve views and misc
Currently translated at 100.0% (99 of 99 strings) Translation: payroll-15.0/payroll-15.0-hr_payroll_period Translate-URL: https://translation.odoo-community.org/projects/payroll-15-0/payroll-15-0-hr_payroll_period/es/
|
Hi @appstogrow, @nimarosa, |
dreispt
force-pushed
the
18.0-mig-hr_payroll_period
branch
from
a2df588 to
47be6a4
Compare
dreispt
force-pushed
the
18.0-mig-hr_payroll_period
branch
from
47be6a4 to
a2e952b
Compare
|
NOTE: after working on it, my feeling is that this module should be discontinued. So I moved this to Draft, as it is not my intention to have it merged. |
|
@dreispt why do you think we should discontinue this module? I think is useful for people who have different payment schedules or periods and reduce the error selecting them manually. But I'm curious of why you think it's not worth to merge, maybe you have a better way to offer that functionality? |
|
I'm not against adding the concept, I dislike the implementation; I see a lot of complexity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.