update sponsors "what's next steps"

playframework · Nov 6, 2023 · bc97b0b · bc97b0b
1 parent ba80a09
commit bc97b0b
Showing 1 changed file with 2 additions and 6 deletions.
diff --git a/app/views/sponsors.scala.html b/app/views/sponsors.scala.html
@@ -91,8 +91,8 @@ <h2>What will the project do with the money?</h2>
             <section>
                 <h2>What are the next steps?<br/></h2>
                 <p>
-                    <i>(December 2021)</i><br/>
-                    Please have a look at our <a href="//github.com/orgs/playframework/projects/1">GitHub project board</a> to see what is happening and what needs to be worked on to transform Play to a community-led organization.
+                    <i>(Updated in November 2023)</i><br/>
+                    Please have a look at our <a href="//github.com/orgs/playframework/projects/3">GitHub project board</a> to see what is happening and what needs to be worked on to transform Play to a community-led organization.
                     We also got asked about a roadmap and priorities regarding Play's development goals:
                 </p>
                 <ul>
@@ -114,10 +114,6 @@ <h2>What are the next steps?<br/></h2>
                         We plan to support Scala 3 as well. There is quite an interest in the community and also people willing to work on that. If everything goes well, we might see support for Scala 3 in Play 2.9 already.
                         We <a href="//github.com/playframework/playframework/pull/10956">dropped support</a> for Scala 2.12 and sbt <=1.3 in the main branch already, to make it easier to cross build Play against Scala 3.
                     </li>
-                    <li>
-                        <b>New releases for Play 2.7 or older</b><br/>
-                        We recognized some people wish that old Play versions should be maintainend longer, at least they should receive security and critical bug fixes. However that is a matter of who can invest time to maintain these old versions and therefore more or less depends on funding of the project. So if you want to see releases of older Play versions, please support the project financially.
-                    </li>
                     <li>
                         <b>Maintaining a stable API</b><br/>
                         Right now, there is no plan to introduce any groundbreaking API changes. The plan for now is to make sure that Play stays maintained to get minor releases out and to finally cut Play 2.9 in the upcoming months. So, there is no plan to drive Play into a new direction. Of course there will very likely be new features, but after talking to companies and users that actively use Play in production, the goal right now is more that there are contributors that keep Play maintained in regards of supporting newest sbt/JVM/Scala versions, security fixes and new minor releases with fixes and major releases with new features wished by the community.