Skip to content

Conversation

@VeckoTheGecko
Copy link
Contributor

This PR renames the breaking changes file to be the migration guide so that its visible in the documentation website.

Once development has stabilised (or in the week leading up to the parcels event) we can flesh this out with code examples.

  • Chose the correct base branch (v4-dev for v4 changes)
  • Fixes none

Comment on lines +13 to +14
Release Notes <https://github.com/OceanParcels/Parcels/releases>
Parcels v4.0 Migration Guide <v4-migration>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I wasn't 100% sure where this should go. This was the best place I could think of. Other projects don't really have a standard place to put this - zarr has a dedicated page in their "user guide", uses a release notes section of their website.

nojit
TODO
Parcels v4 Project Board <https://github.com/orgs/OceanParcels/projects/5>
Parcels v4 migration guide <../community/v4-migration>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Linking it as well from this page, but once v4 is released this whole "v4" section will be deleted (we probably might want to do other restructuring as well, to be decided/discussed later)

Copy link
Member

@erikvansebille erikvansebille left a comment

Choose a reason for hiding this comment

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

Looks good!

@VeckoTheGecko VeckoTheGecko merged commit 5b603b1 into v4-dev Sep 9, 2025
9 checks passed
@VeckoTheGecko VeckoTheGecko deleted the v4-migration-guide branch September 9, 2025 09:20
@github-project-automation github-project-automation bot moved this from Backlog to Done in Parcels development Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants