#1494 new
Peter Hilton

Add FAQs about future Play 1.x plans

Reported by Peter Hilton | April 16th, 2012 @ 08:44 PM | in 1.4.x

There are various posts on the mailing list with the same questions and FUD about Play 1.x, including

At this stage, it would be useful to answer the following new FAQs.

  • Has Play 1.x been abandoned?
  • Can I get support for Play 1.x?
  • Will there be new Play 1.x releases?
  • When will new features be added to Play 1.x?
  • Why isn’t there a Play 2.x migration guide?

Pull requests should be for https://github.com/playframework/play/blob/master/documentation/man...

Play 2.x will probably get its own FAQ at some point, but that’s a whole different topic.

Comments and changes to this ticket

  • Peter Hilton

    Peter Hilton April 17th, 2012 @ 07:22 AM

    Has Play 1.x been abandoned?

    No. Play is currently used in production on many commercial software development projects that have no plans to migrate to Play 2.x, and there are core developers and community members who are committed to keeping Play 1.x alive.

    Can I get support for Play 1.x?

    Yes. The Google Group and Stack Overflow represent a large body of Play 1.x knowledge, and the on-line community is still actively answering questions about using Play 1.x. In addition, commercial support (consultancy and training) is available from companies such as Lunatech Research that use Play on customer development projects.

    Will there be new Play 1.x releases?

    Yes. There will be new releases from the Play 1.2.x branch to provide bug fixes and minor improvements. This is a stable codebase and ideal for projects that want stability and backward compatibility in the future. This the same situation as most enterprise products, such as application servers and relational databases, in which each generation (incompatible major release) is feature complete after a couple of minor releases, and then continues to be supported with a series of maintenance releases.

    When will new features be added to Play 1.x?

    Play 1.x is by all accounts feature complete: the core framework includes the functionality required to build a web application, and Play modules and plug-ins make it possible to enhance or replace Play functionality. Most candidate new features belong in modules, because otherwise they would bloat the core with functionality that most users do not need.

    Why isn’t there a Play 2.x migration guide?

    There is no Play 2.x migration guide because no-one has contributed one yet, and because no-one is being forced to migrate. As of April 2011, Play 2.0 is still new and relatively few Play 1.x projects have migrated to Play 2.0, and there is therefore relatively little community knowledge on the subject. Meanwhile, the Play 2.x documentation wiki already contains initial information, such as Play 2.0 alternatives for Play 1.x features

  • notalifeform (at gmail)

    notalifeform (at gmail) April 21st, 2014 @ 07:58 PM

    • Milestone changed from 1.3 to 1.4.x

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Pages