Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] update sponsors "what's next steps" #563

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[WIP] update sponsors "what's next steps" #563

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions app/views/sponsors.scala.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand All @@ -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.
Expand Down
Loading