Open santosomar opened 2 weeks ago
@santosomar: I think those are two distinct things (as mentioned in https://github.com/oasis-tcs/openeox/pull/13#discussion_r1558029586)
This also reflects what is currently done by many open source projects (not backporting new features, but keeping security up-to-date for a while) and commercial products (e.g. Windows 10)
You are right, @tschmidtb51 . Some companies use the same milestone and not others. I am separating both of them and creating a new issue.
I created #32 for the "End of vulnerability support"
End-of-Software Maintenance (EOSM) marks the date when a vendor or maintainer ceases to provide maintenance updates for a specific software product. Maintenance updates typically include minor bug fixes, performance improvements, and minor feature enhancements. After the EOSM date, the software will no longer receive these updates, although security patches and critical fixes may still be provided until the End-of-Security Vulnerability Support (EOSVS) date.
Consider a project management software called "TaskMaster" developed by SoftCorp. SoftCorp announces that the End-of-Software Maintenance for TaskMaster version 2.5 will be on March 31, 2024. After this date, SoftCorp will no longer provide maintenance updates such as bug fixes or minor enhancements for TaskMaster 2.5. However, security patches will still be issued until the End-of-Security Vulnerability Support date of March 31, 2025. Users are advised to upgrade to TaskMaster version 3.0 to continue receiving full maintenance and support.
This is a follow up of #13
Let's define each element and work on their definitions in separate GitHub issues. This issue will focus on defining:
End-of-Software Maintenance