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

Make sure upgrade docs for each released version have the correct supported upgrade path listed. #304

Open
a-mccarthy opened this issue Mar 23, 2022 · 3 comments
Labels
good first issue Good for newcomers

Comments

@a-mccarthy
Copy link
Collaborator

According to the upgrade section of the release docs in the Harbor repo, https://github.com/goharbor/harbor/blob/main/RELEASES.md#upgrade-path-and-support-policy

The upgrade path for Harbor is (1) 2.2.x patch releases are always compatible with its major and minor version. For example, previous released 2.2.x can be upgraded to most recent 2.2.3 release. (2) Harbor only supports two previous minor releases to upgrade to current minor release. For example, 2.3.0 will only support 2.1.0 and 2.2.0 to upgrade from, 2.0.0 to 2.3.0 is not supported. One should upgrade to 2.2.0 first, then to 2.3.0. The Harbor project maintains release branches for the three most recent minor releases, each minor release will be maintained for approximately 9 months.

We should make sure the each of the following pages lists the correct versions of the supported upgrade path, and links to previous upgrade pages.

@a-mccarthy a-mccarthy added the good first issue Good for newcomers label Mar 30, 2022
@a-mccarthy
Copy link
Collaborator Author

Here is the updates i made for the 2.5 release, https://goharbor.io/docs/edge/administration/upgrade/

@a-mccarthy
Copy link
Collaborator Author

@eugeneivanov101

@harsh-G13
Copy link

Is this issue still open? @a-mccarthy ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants