Skip to content

[18.0][MIG] maintenance_team_hierarchy: Migration to 18.0#517

Open
ypapouin wants to merge 16 commits intoOCA:18.0from
decgroupe:18.0-mig-maintenance_team_hierarchy
Open

[18.0][MIG] maintenance_team_hierarchy: Migration to 18.0#517
ypapouin wants to merge 16 commits intoOCA:18.0from
decgroupe:18.0-mig-maintenance_team_hierarchy

Conversation

@ypapouin
Copy link
Copy Markdown
Contributor

Basic migration task.

  • Added the parent field in the list view (editable)
  • Also added the "View Form" shortcut using open_form_view=True
image

@ypapouin ypapouin force-pushed the 18.0-mig-maintenance_team_hierarchy branch from 06dc8db to 0d501ce Compare October 14, 2025 09:10
@ypapouin ypapouin mentioned this pull request Oct 21, 2025
16 tasks
@ypapouin ypapouin force-pushed the 18.0-mig-maintenance_team_hierarchy branch from 0d501ce to 42c7ede Compare October 28, 2025 12:02
@ypapouin ypapouin force-pushed the 18.0-mig-maintenance_team_hierarchy branch from 42c7ede to 8c29f1c Compare February 18, 2026 09:12
Comment thread maintenance_team_hierarchy/views/maintenance_team.xml Outdated
Comment thread maintenance_team_hierarchy/models/maintenance_team.py
Copy link
Copy Markdown
Contributor

@sergiocorato sergiocorato left a comment

Choose a reason for hiding this comment

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

@ypapouin
Copy link
Copy Markdown
Contributor Author

ypapouin commented Apr 3, 2026

@sergiocorato , I don't see anything that could be squashed according to the Wiki

@sergiocorato
Copy link
Copy Markdown
Contributor

sergiocorato commented Apr 3, 2026

@sergiocorato , I don't see anything that could be squashed according to the Wiki

example, these should be merged in the first:

Screenshot(208)

other example, these 3 should be merged in the first too:

Screenshot(210)

@ypapouin
Copy link
Copy Markdown
Contributor Author

ypapouin commented Apr 3, 2026

In the Wiki example, only commits with same commit message are squashed and that make sense

etobella and others added 5 commits April 3, 2026 16:01
[UPD] Update maintenance_team_hierarchy.pot
[UPD] Update maintenance_team_hierarchy.pot

[UPD] README.rst

Update translation files

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: maintenance-13.0/maintenance-13.0-maintenance_team_hierarchy
Translate-URL: https://translation.odoo-community.org/projects/maintenance-13-0/maintenance-13-0-maintenance_team_hierarchy/
@ypapouin ypapouin force-pushed the 18.0-mig-maintenance_team_hierarchy branch from 8c29f1c to a5fc78b Compare April 3, 2026 14:07
@sergiocorato
Copy link
Copy Markdown
Contributor

In the Wiki example, only commits with same commit message are squashed and that make sense

I'm referring to this part for the first example:

Screenshot(211)

@sergiocorato
Copy link
Copy Markdown
Contributor

sergiocorato commented Apr 3, 2026

To this part for the second:

Screenshot(212)

@ypapouin
Copy link
Copy Markdown
Contributor Author

ypapouin commented Apr 3, 2026

Ok, so does that mean that , for example, I should squash these 3 commits together ?
(and keep only the message "[MIG] maintenance_team_hierarchy: Migration to 15.0")

image

@sergiocorato
Copy link
Copy Markdown
Contributor

sergiocorato commented Apr 7, 2026

Ok, so does that mean that , for example, I should squash these 3 commits together ? (and keep only the message "[MIG] maintenance_team_hierarchy: Migration to 15.0")

This screen has not enough informations, if you watch here in "commits" section you can see as explained before and as found in migration guidelines, below what I should do:

Screenshot(216)

@ypapouin ypapouin force-pushed the 18.0-mig-maintenance_team_hierarchy branch from a5fc78b to bf3760e Compare April 7, 2026 11:53
@ypapouin ypapouin requested a review from sergiocorato April 7, 2026 11:56
@ypapouin
Copy link
Copy Markdown
Contributor Author

ypapouin commented Apr 7, 2026

@sergiocorato , thank you for taking time to explain all this.
I think that everything is now properly squashed.

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.

8 participants