Skip to content

fix: bad link in versions.md #53

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.

Sign up for GitHub

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

Open
aespitia wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: bad link in versions.md #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/versions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,12 @@ date: 2023-12-13

## Versioning Strategy

**ScottPlot does not use [semantic versioning](semver.org).** Instead, version numbers are thoughtfully incremented to signal the likelihood that effort will be required to upgrade. Efforts are made to maximize backward compatibility, but **development prioritizes moving toward a high quality and intuitive API** over preventing existing users from having to modify code to upgrade.
**ScottPlot does not use [semantic versioning](https://semver.org).** Instead, version numbers are thoughtfully incremented to signal the likelihood that effort will be required to upgrade. Efforts are made to maximize backward compatibility, but **development prioritizes moving toward a high quality and intuitive API** over preventing existing users from having to modify code to upgrade.

**Naming:** ScottPlot x.y.z (major.minor.build)

* **Build version bump:** The overwhelming majority of users will be able to upgrade effortlessly without requiring code modification. A **small subset of users** who use advanced ScottPlot features to achieve extreme customization of appearance or interactive behavior may be required to modify source code after upgrading.

* **Minor version bump:** Significant changes to the API will require **many users** to modify source code files. However, many users will be able to upgrade effortlessly without requiring code modification.

* **Major version bump:** Significant changes the API require **all users** to modify most source code files and refer to new documentation. Unless the SkiaSharp is replaced with a different rendering system it unlikely ScottPlot will experience a major version bump.
* **Major version bump:** Significant changes the API require **all users** to modify most source code files and refer to new documentation. Unless the SkiaSharp is replaced with a different rendering system it unlikely ScottPlot will experience a major version bump.