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

Update 2.0.0.md #16015

Merged
merged 2 commits into from
May 13, 2024
Merged

Update 2.0.0.md #16015

merged 2 commits into from
May 13, 2024

Conversation

gvkries
Copy link
Contributor

@gvkries gvkries commented May 8, 2024

Stronger wording that an upgrade to 1.8 is required before 2.0.

Stronger wording that an upgrade to 1.8 is required before 2.0.
@@ -4,7 +4,7 @@ Release date: Not yet released

## Upgrade Instructions
Copy link
Member

Choose a reason for hiding this comment

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

Important Upgrade Instructions

@@ -4,7 +4,7 @@ Release date: Not yet released

## Upgrade Instructions

Before upgrading to Orchard Core 2.0, you should first upgrade to 1.8, address any warnings, and only then upgrade to 2.0. Be sure to review the list of breaking changes documented below to ensure a seamless transition.
Copy link
Member

Choose a reason for hiding this comment

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

Prior to making the leap to Orchard Core 2.0, it's crucial to follow a step-by-step upgrade process. Begin by upgrading your current version to 1.8, resolving any obsolete warnings encountered along the way, and guaranteeing that every site successfully operates on version 1.8.3. This approach ensures that all sites are seamlessly transitioned to 1.8. Subsequently, proceed with confidence to upgrade to 2.0. Prior to initiating this upgrade, thoroughly review the documented list of breaking changes provided below to facilitate a smooth and hassle-free transition.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, thank you 👍

Copy link
Member

@MikeAlhayek MikeAlhayek left a comment

Choose a reason for hiding this comment

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

some suggestions on improving the verbiage

@Piedone
Copy link
Member

Piedone commented May 8, 2024

FYI, since the Windows build failed the first time: #16018

@Piedone
Copy link
Member

Piedone commented May 9, 2024

At this point, perhaps just open your own PR, Mike :).

Applied suggested changes.
@MikeAlhayek MikeAlhayek merged commit d815446 into OrchardCMS:main May 13, 2024
11 checks passed
@gvkries gvkries deleted the patch-1 branch May 24, 2024 11:25
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.

3 participants