This is an automated email from the ASF dual-hosted git repository.

jamesfredley pushed a commit to branch restore-support-schedule-page
in repository https://gitbox.apache.org/repos/asf/grails-static-website.git

commit 26b2636e2f49f83c1e0dbe0e46ab58da256a8a1e
Author: James Fredley <[email protected]>
AuthorDate: Tue Oct 28 11:10:12 2025 -0400

    Restore support schedule page and stylesheet
    
    Restore support schedule HTML page detailing Grails framework lifecycle 
stages and version support timelines. Adds corresponding CSS for table and 
layout styling.  Update with ASF and latest release changes.
---
 assets/stylesheets/support-schedule.css |  20 +++++
 pages/support-schedule.html             | 138 ++++++++++++++++++++++++++++++++
 2 files changed, 158 insertions(+)

diff --git a/assets/stylesheets/support-schedule.css 
b/assets/stylesheets/support-schedule.css
new file mode 100644
index 00000000000..f7eb0ab0417
--- /dev/null
+++ b/assets/stylesheets/support-schedule.css
@@ -0,0 +1,20 @@
+table.support-schedule {
+    width: 100%;
+    overflow-x: auto;
+}
+
+.twocolumns.support-schedule {
+    background-color: #ffffff;
+}
+
+table.support-schedule tr:nth-child(even) {
+    background-color: #dddddd;
+}
+
+table.support-schedule td {
+    color: #545454;
+    border-left: none;
+    border-right: none;
+    border-bottom: none;
+    border-top: none;
+}
\ No newline at end of file
diff --git a/pages/support-schedule.html b/pages/support-schedule.html
new file mode 100644
index 00000000000..e7bb9e3ab79
--- /dev/null
+++ b/pages/support-schedule.html
@@ -0,0 +1,138 @@
+title: Support Schedule | Apache Grails&reg;  Framework
+CSS: /stylesheets/support-schedule.css
+keywords: grails,version,support,schedule,eol,end-of-life,maintenance
+description: Support schedule for the Grails&reg; application framework
+---
+<div class='headerbar chalicesbg'>
+    <div class='content'>
+        <h1>Support Schedule</h1>
+    </div>
+</div>
+<div class='content'>
+    <article>
+        <div class='twocolumns support-schedule'>
+                <div class='post no-border'>
+                    <section>
+                        <p>
+                            <strong>
+                                The Apache Grails<sup>&reg;</sup> Community is 
committed to the continued innovation, development, maintenance, and support of 
the Grails framework.
+                            </strong>
+                        </p>
+                        <p>
+                            Our goal is to provide Grails framework users the 
support they need while maintaining as much focus as possible on innovation.
+                        </p>
+                    </section>
+                    <section>
+                        <h2 class="subsection-header">Lifecycle Stages</h2>
+                        <p>
+                            Versions of the Grails framework may fall into one 
of three lifecycle stages:
+                        </p>
+                        <ul>
+                            <li>Active Development</li>
+                            <li>Active Maintenance</li>
+                            <li>End of Support</li>
+                        </ul>
+                    </section>
+                    <section>
+                        <h3 class="subsection-header">Active Development</h3>
+                        <p>
+                            Grails versions that are in “Active Development” 
receive regular updates, including new features, performance enhancements, and 
bug fixes. These versions receive a majority of our time and effort investment 
and represent the latest and greatest that the Grails framework has to offer.
+                        </p>
+                        <p>
+                            We recommend that new and existing Grails 
applications be built with or upgraded to these versions.
+                        </p>
+                    </section>
+                    <section>
+                        <h3 class="subsection-header">Active Maintenance</h3>
+                        <p>
+                            "Active Maintenance" releases receive limited bug 
fixes and patches, mostly focused around the resolution of critical security 
advisories. New features, performance improvements, and minor bug fixes are 
unlikely.
+                        </p>
+                        <p>
+                            We recommend that organizations whose Grails 
applications depend on a release that's in Active Maintenance upgrade to the 
latest “Active Development” version in order to make use of the latest features 
the framework has to offer.
+                        </p>
+                    </section>
+                    <section>
+                        <h3 class="subsection-header">End of Support</h3>
+                        <p>
+                            Once a Grails framework version moves from "Active 
Maintenance" to "End of Support", it is unlikely to receive additional updates.
+                        </p>
+                        <p>
+                            We recommend that organizations which are relying 
on an End of Support version of the Grails framework upgrade to a "Active 
Maintenance" or "Active Development" version as soon as possible.
+                        </p>
+                    </section>
+                    <section>
+                        <h3 class="subsection-header">Commercial Support</h3>
+                        <p>Please note that the Apache Software Foundation 
does not offer commercial support for Apache Grails or related applications.
+                        </p>
+                        <p>
+                            We understand that there are situations in which 
it may be difficult to keep an application up to date with the latest supported 
versions of the Grails framework. For these situations, <a 
href="support.html">commercial support options</a> can help address critical 
security advisories for the version of the Grails framework that you are 
utilizing.
+                        </p>
+                    </section>
+                </div>
+            </div>
+
+        <table class="support-schedule">
+            <tr>
+                <th>Version</th>
+                <th>Stage</th>
+                <th>Initial Release</th>
+                <th>Last Release</th>
+                <th>Maintenance Support Through</th>
+            </tr>
+            <tr>
+                <td>7</td>
+                <td>Active Development</td>
+                <td>Oct 2025</td>
+                <td>Ongoing</td>
+                <td>Jun 2026</td>
+            </tr>
+            <tr>
+                <td>6</td>
+                <td>End of Support</td>
+                <td>Jul 2023</td>
+                <td>Jan 2025<br/>(6.2.3)</td>
+                <td>Mar 2025</td>
+            </tr>
+            <tr>
+                <td>5</td>
+                <td>End of Support</td>
+                <td>Oct 2021</td>
+                <td>Jan 2024<br/>(5.3.6)</td>
+                <td>Mar 2025</td>
+            </tr>
+            <tr>
+                <td>4</td>
+                <td>End of Support</td>
+                <td>Jul 2019</td>
+                <td>Mar 2024<br/>(4.1.4)</td>
+                <td>Mar 2024</td>
+            </tr>
+            <tr>
+                <td>3</td>
+                <td>End of Support</td>
+                <td>Mar 2015</td>
+                <td>Aug 2022<br/>(3.3.16)</td>
+                <td>Sep 2021</td>
+            </tr>
+            <tr>
+                <td>2</td>
+                <td>End of Support</td>
+                <td>Dec 2011</td>
+                <td>Mar 2017<br/>(2.5.6)</td>
+                <td>Jun 2021</td>
+            </tr>
+            <tr>
+                <td>1</td>
+                <td>End of Support</td>
+                <td>Feb 2008</td>
+                <td>May 2012<br/>(1.3.9)</td>
+                <td>Not Available</td>
+            </tr>
+        </table>
+        <div class="support-schedule-table-annotations">
+            <p><sup>* - Future dates are subject to change</sup></p>
+        </div>
+
+    </article>
+
+</div>
\ No newline at end of file

Reply via email to