"The duration of the maintenance window will vary from product to product and release to release. By default, versions will remain under maintenance until the next major version enters maintenance, or 1 year passes, whichever is longer. Therefore, at any given time, the current major version and previous major version will both be supported, as well as older major versions that have been in maintenance for less than 12 months. Please note that, maintenance windows are influenced by the support schedules for dependencies the software includes, community input, the scope of the changes introduced by the new version, and estimates for the effort required to continue maintenance of the previous version."
For now we have this :
endoflife.date/opensearch
Let me know if it looks good
Hello @adriens - I recommend checking out our Releases page for official, up-to-date information on this topic: opensearch.org/releases.html
"The duration of the maintenance window will vary from product to product and release to release. By default, versions will remain under maintenance until the next major version enters maintenance, or 1 year passes, whichever is longer. Therefore, at any given time, the current major version and previous major version will both be supported, as well as older major versions that have been in maintenance for less than 12 months. Please note that, maintenance windows are influenced by the support schedules for dependencies the software includes, community input, the scope of the changes introduced by the new version, and estimates for the effort required to continue maintenance of the previous version."
Hope this helps.
Hi Kris, sure ! It helps a lot, it should help improve
endoflife.dateinitiative :OpenSearch is a very living and fast growing product. Still it seems we could improve some of its eols datas :
By adding some resources helping get more data about :
OpenSearch | endoflife.date
Check End of Life, Support Schedule, and release timelines for AlmaLinux, Alpine Linux, Amazon Linux, Android OS, Angular, Ansible-core, Ansible, antiX, Apache Airflow, Apache Cassandra, Apache Groovy, Apache HTTP Server, API Platform, Azure DevOps, Blender, Bootstrap, CakePHP, CentOS, CFEngine, Citrix Virtual Apps and Desktops, Adobe ColdFusion, Composer, Consul, Google Container-Optimized OS (COS), Couchbase Server, Debian, Devuan, Django, Docker Engine, .NET, .NET Framework, Drupal, Drush, Amazon EKS, Elasticsearch, Electron, Elixir, Ember, EuroLinux, Fedora Linux, FFmpeg, Filebeat, FileMaker, Firefox, FortiOS, FreeBSD, GitLab, Google Kubernetes Engine, Go, Godot, Gradle, Grafana, HAProxy, Vault, Apache HBase, Intel Processors, Internet Explorer, Apple iOS, Apple iPadOS, iPhone, Java/OpenJDK, Jenkins, jQuery, KDE Plasma, Amazon Kindle, Kotlin, Kubernetes, Laravel, LibreOffice, LineageOS, Linux Kernel, Linux Mint, Apache Log4j, Looker, macOS, Magento, MariaDB, Mattermost, MediaWiki, MongoDB Server, Moodle, Microsoft Exchange, Microsoft SharePoint, Microsoft SQL Server, Mule Runtime, MX Linux, MySQL, NetBSD, Nextcloud, nginx, nix, NixOS, Node.js, Nokia Mobile, Nomad, NumPy, Nutanix AOS, Nutanix Files, Nutanix Prism Central, NVIDIA Driver, NVIDIA GPUs, Microsoft Office, OpenBSD, OpenSearch, OpenSSL, openSUSE, OpenZFS, Oracle Linux, Palo Alto Networks GlobalProtect App, Palo Alto Networks PAN-OS, Palo Alto Networks Cortex XDR agent, PCI-DSS, Perl, PHP, Google Pixel, Postfix, PostgreSQL, PowerShell, Python, Qt, Quarkus, RabbitMQ, React, Netgear ReadyNAS, Red Hat Enterprise Linux, Redis, Redmine, Rocky Linux, ROS, Roundcube Webmail, Ruby on Rails, Ruby, Samsung Mobile, Slackware Linux, SUSE Linux Enterprise Server, Apache Solr, Splunk, Spring Boot, Spring Framework, Microsoft Surface, Symfony, Tarantool, Telegraf, Terraform, Apache Tomcat, Twig, TYPO3, Ubuntu, Unity, UnrealIRCd, Varnish, Visual Studio, VMware ESXi, VMware Horizon, VMware Site Recovery Manager, VMware vCenter Server, Vue, Wagtail, Apple watchOS, Windows, Windows Embedded, Windows Server, WordPress, Yocto Project, Zabbix, Apache ZooKeeper, etc at one place.