Skip to content

armgit / spree

Public Imported from GitHub
0

Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.

Ad Upgrade page

Damian Legawiec2f2e80a6f79d
diff --git a/guides/src/content/developer/upgrades/index.md b/guides/src/content/developer/upgrades/index.md
new file mode 100644
index 0000000000..ab6451512b
--- /dev/null
+++ b/guides/src/content/developer/upgrades/index.md
@@ -0,0 +1,39 @@
+---
+title: Upgrading Spree
+section: upgrades
+order: 0
+---
+
+## Overview
+
+Keeping your Spree installation up-to-date is essential to keep it safe and secure. Each Spree version brings new features, enhancements and bugfixes so it's greatly beneficial for you and your clients to upgrade frequently.
+
+The upgrade process is fairly easy and well described. Of course it all boils down to the level of customizations and the way you've customized your Spree applications.
+
+We strongly advise upgrading Spree incrementally, rather than in one big go.
+
+## Support
+
+If you're stuck and would want get some professional help, you can [contact us directly](https://spreecommerce.org/contact/) and request a quote for our constulting services.
+
+## Release types
+
+Spree development follows a shifted version of [Semantic Versioning](https://semver.org/):
+
+**Patch Z, eg. 4.2.1**
+
+Only bug fixes, no API changes, no new features. Except as necessary for security fixes.
+
+**Minor Y, eg. 4.2.0**
+
+New features, may contain API changes (Serve as major versions of Semver). Breaking changes are paired with deprecation notices in the previous minor or major release.
+
+**Major X, eg. 4.0.0**
+
+New features, will likely contain API changes. The difference between Spree minor and major releases is the magnitude of breaking changes, and usually reserved for special occasions.
+
+## Security
+
+Our Security policy is [described here](/developer/security/security.html).
+
+When a release series is no longer supported, it's your own responsibility to deal with bugs and security issues. We may provide backports of some critical security fixes.
diff --git a/guides/src/content/developer/upgrades/upgrade_guides.md b/guides/src/content/developer/upgrades/upgrade_guides.md
index ca2e7c79ea..16f3641456 100644
--- a/guides/src/content/developer/upgrades/upgrade_guides.md
+++ b/guides/src/content/developer/upgrades/upgrade_guides.md
@@ -1,6 +1,7 @@
---
title: "All Upgrade Guides"
section: upgrades
+hidden: true
---
## Upgrade Guides