Skip to content

Commit

Permalink
removed references to removed section
Browse files Browse the repository at this point in the history
  • Loading branch information
reebhub committed Dec 18, 2024
1 parent ecc221a commit 98da595
Showing 1 changed file with 0 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,6 @@
{PANEL: Migration from RavenDB 5.x to 6.x}

* RavenDB `6.x` supports in-place migration of data from RavenDB `5.x`.
* During the first startup after [replacing the binaries](../../migration/server/data-migration#replacing-the-binaries) with the new ones, the data will migrate automatically.
* RavenDB `5.x` product licenses **do not apply** to RavenDB `6.x`.
To upgrade a valid `5.x` license to a RavenDB `6.x` license,
please use the **License upgrade tool** [as explained here](../../start/licensing/replace-license#upgrade-a-license-key-for-ravendb-6.x).
Expand All @@ -38,7 +37,6 @@ and the migrated data will no longer be accessible via RavenDB `5.x`.
It is also possible to upgrade directly from version `4.x` to `6.x`,
but it is recommended to first upgrade RavenDB `4.x` to `5.x`, and then proceed from `5.x` to `6.x`.
{INFO/}
* During the first startup after [replacing the binaries](../../migration/server/data-migration#replacing-the-binaries) with the new ones, the data will migrate automatically.
* RavenDB `4.x` product licenses **do not apply** to RavenDB `6.x`.
To upgrade a valid `4.x` license to a RavenDB `6.x` license,
please use the **License upgrade tool** [as explained here](../../start/licensing/replace-license#upgrade-a-license-key-for-ravendb-6.x).
Expand Down

0 comments on commit 98da595

Please sign in to comment.