Overview
This Inrupt Product Lifecycle and Maintenance Policy (“Policy”) describes the support lifecycle and release processes for all Inrupt Products.
1. Definitions
The following terms have the following meanings when used in this Policy.
1.1 ESS Server
“ESS Server" means the Inrupt Enterprise Solid Server.
1.2. Versioning Scheme:
Inrupt Products follow the Semver versioning scheme, described at https://semver.org/
“Major Release”
“Major Release” means a version of an Inrupt product identified by a change in the number to the left of the first decimal point (X.x.x). Major Releases may contain backwards breaking compatibility changes to the product.
“Minor Release”
“Minor Release” means a version of an Inrupt product identified by a change in the middle number in between the two decimal points (x.X.x). Minor releases preserve full backwards compatibility within a Major Release.
"Patch Release"
"Patch Release" means a version of the ESS Server identified by a change in the number to the right of the second decimal point (x.x.X). Patch versions preserve full backwards compatibility within a Major Release.
2. Major & Minor Release life-cycle
The life-cycle for major and minor versions of Inrupt Software consists of 4 phases, which are outlined below.
2.1 Developer Preview / Alpha / Beta (Phase 1)
During this phase, the software should not be used in production environments and is meant for early access and feedback purposes only. It is possible for future releases to introduce breaking changes.
2.2 General Availability / Full Support (Phase 2)
During this phase, the software is fully supported.
2.3 Deprecated (Phase 3)
Inrupt will make a public announcement when software enters the deprecation phase. During this period, releases are limited to critical bug fixes and security issues only. No new feature development is done on deprecated major versions of products. A version is deprecated once it is no longer the latest major or minor version or 6 months after its release, whichever comes later. We recommend customers upgrade to a fully supported version once the version they are on is deprecated.
2.4 End-of-Life (Phase 4)
All Major and Minor Releases will be supported for a minimum of 12 months. Major and Minor versions of Inrupt software reach end-of-life 6 months after deprecation or when that version has fallen 2 major or minor versions behind the latest version, whichever comes later.
Inrupt will make a public announcement when software enters the end-of-life phase. When a major product version reaches End-of-Life, it will no longer receive minor updates or patch releases. When a minor product version reaches end-of-life, it will no longer receive patch releases. In both cases the Inrupt team will not provide support for it. Use of software which has reached end-of-life is done at the user’s own risk.
2.5 Lifecycle Visualization
The following is a visual illustration of the major version life-cycle. Please note that the timelines shown below are illustrative and not binding.
3. Patch Version Lifecycle
Patch Version Lifecycle
All Patch Releases within a Minor Release series will be supported in the same timeframe as the Minor Release they correspond to, unless the relevant support policy states otherwise.
4. Security
Penetration Testing
The Inrupt Enterprise Solid Server is certified by third party penetration testing annually. The independent certification letter is available from Inrupt upon request.
Vulnerability Testing and Response
Inrupt runs continuous scanning for vulnerabilities in its infrastructure and code, with a response policy and procedure published at https://www.inrupt.com/security/.
Incident Response and Reporting
For more details on incident response, vulnerabilities, current list of advisories, and CVE reporting please visit https://www.inrupt.com/security/
5. Testing
All Inrupt products and services undergo a suite of functional and nonfunctional testing, regression testing, and formal security reviews. Inrupt uses standard and customary tooling for testing for safety and security. Details on our policies and processes are available upon request.
6. Maintenance Policies
6.1 Enterprise Solid Server
|
Release |
Release Date |
Status |
End of Life Date |
|
1.0.x |
November 2020 |
End of Life |
February 2022 |
|
1.1.x |
April 2021 |
Deprecated |
December 2022 |
|
2.0.x |
June 2022 |
Fully Supported |
TBD |
6.2 Developer Tools
Javascript Client Libraries
|
Package Name |
Release |
Release Date |
Status |
End of Life Date |
|
solid-client-js |
1.x |
November 2020 |
Full Support |
- |
|
solid-client-authn |
1.x |
November 2020 |
Full Support |
- |
|
solid-client-notifications-js |
1.x |
June 2022 |
Full Support |
- |
|
solid-client-access-grants |
1.x |
June 2022 |
Full Support |
- |
|
artifact-generator |
2.x |
June 2022 |
Full Support |
- |
|
generate-oidc-token |
0.x |
June 2021 |
Deprecated |
June 2023 |
|
artifact-generator |
1.x |
June 2021 |
End of Life |
June 2022 |
|
solid-client-notifications-js |
0.x |
June 2021 |
End of Life |
June 2022 |
|
solid-client-access-grants |
0.x |
October 2021 |
End of Life |
June 2022 |
React SDK
|
Package Name |
Release |
Release Date |
Status |
End of Life Date |
|
solid-ui-react |
2.x |
November 2020 |
Full Support |
- |
6.3 PodBrowser
|
Release |
Release Date |
Status |
End of Life Date |
|
1.0.x |
November 2020 |
End of Life |
February 2022 |
|
1.1.x |
April 2021 |
Deprecated |
December 2022 |
|
2.0.x |
June 2022 |
Full Support |
TBD |
7. Licensing
Enterprise Solid Server
The Enterprise Solid Server utilizes an Inrupt ESS License. Details on the license are available upon request.
Developer Tools
All Inrupt Developer Tools are licensed under the MIT License.
PodBrowser
PodBrowser is licensed under the MIT License.
8. Notifications
To be notified of any amendments made to this policy, please subscribe to the Inrupt Product Mailing List. All Customers with existing agreements with Inrupt will be notified automatically.