Play Sprint Plan 2019-03-25

[marcospereira]

Previous sprint plans

Dates

• Start: 2019-03-25
• End: 2019-04-05

Absences

• @marcospereira:
  • Support: April 1 – 5, 2019
• @ignasi35:
  • Support: March 25 – 29, 2019
• @dwijnand:
  • Off: March 29 – April 2, 2019

Objectives

Cleanups

• Evaluate the impact of Lagom 1.5 on the Operations training (Email thread) @renatocaval
• Play: Release 2.7.1 Release Play 2.7.1 #52 @marcospereira
• Upgrade builds to sbt 1 Upgrade the builds from sbt 0.13 to sbt 1 #14
  • Play Use sbt 1 to build Play itself playframework#8383 @marcospereira
  • Play 2.6 [2.6.x] Use sbt 1 to build Play itself (#9001) playframework#9140
  • Lagom Use sbt 1 to build Lagom itself lagom/lagom#1329 @dwijnand
  • lagom.com Migrate to sbt 1.x lagom/lagom.github.io#183 @ignasi35
  • omnidoc Upgrade to sbt 1.0 omnidoc#32 @ignasi35
  • play-slick Upgrades to build on sbt 1.0 play-slick#465 @ignasi35
  • scalatestplus-play Update build to use sbt 1.0 (also enables mima) scalatestplus-play#110 and [4.0.x] sbt 1.0 scalatestplus-play#145 @marcospereira @ignasi35
• (unplanned) Cleanup stable branches. Stable branches are not up to date with needs-backport PRs.
  • scalatestplus-play (needed backport and forward-ports)
  • play-ws
  • play-slick
• Drop allow_failures for AdoptOpenJDK 11 (+ update spreadsheet + tracking issue) @dwijnand
  • Don't allow Java 11 to fail cachecontrol#49
  • Don't allow Java 11 to fail play-file-watch#35
  • Don't allow Java 11 to fail twirl#208
  • Fix & don't allow_failure on Java 11 netty-reactive-streams#54
  • Don't allow Java 11 to fail lagom/lagom-akka-discovery-service-locator#63
  • Don't allow Java 11 to fail scalatestplus-play#140
  • play
    • Run scripted tests in AdoptOpenJDK 11 (sbt 1) Run scripted tests on Java 11 playframework#9133
    • Update Akka HTTP to version 10.1.8 akka-http 10.1.8 playframework#9116
  • play-iteratees
  • play-slick Don't allow JDK11 build to fail play-slick#464
  • play-json Don't allow JDK11 build to fail play-json#244
  • play-ws Don't allow JDK11 build to fail play-ws#315
  • lagom Support for Java 11 lagom/lagom#1417
• play-grpc: cross-build for Scala 2.13 Cross-build to Scala 2.13 play-grpc#40
  • blocked on Build for scala 2.13 as well akka/akka-grpc#506
  • blocked on Scala 2.13 support lagom/lagom#1240
    • blocked on slick/slick#1958
    • blocked on akka/alpakka-kafka#540
    • blocked on apache/kafka#5454
• Remove sbteclipse from all the repos Remove sbteclipse-plugin from sample apps #50 @ignasi35
• Set up org-wide GitHub files Setup community health file #47
• Lagom: shopping-cart > hello world lagom/shopping-cart-scala > hello world #33 deferred until further discussed
  • Archive chirper
  • Archive online-auction
    • Add a Play web-gateway in shopping-cart
    • Cassandra example?
  • Is it possible to use shopping-cart to smoke test the deploy to OpenShift?
• TemplateControl: handle Mergify changes Special support for Mergify config changes templatecontrol#113 @dwijnand
• Use scala-steward: Use scala-steward to keep framework and libraries updated #57 Adds Play and Lagom projects scala-steward-org/scala-steward#378
  • Work together with Mergify - deferred. We can start by merging the PRs manually.
• Lagom cron build
  • Fix the build Only run versionSyncCheck if NOT a cron job lagom/lagom#1823
  • Build for 1.5.x branch
• Play cron build is broken @renatocaval - PR: Split cron build extra opts playframework#9124
• g8 scaffolding
  • For Lagom services
  • For Play forms/controllers
• Mergify
  • Do backports - REVERTED: we found issues with Mergify
    Backporting picking more commits then expected Mergifyio/mergify#359
  • Inspect /lagom/ and /playframework/ repositories to add Mergify: https://github.com/playframework/play-meta/blob/master/repos.md
    progress is being tracked here: Review Mergify rules #24
  • PR+tag builds only Disable branch builds playframework#9139
  • PR+tag builds only Build only the tags lagom/lagom#1841
• Fix ssl-config situation Revert ssl-config mistake #4 @dwijnand

Iceland

• Dependency injection for Akka Typed in Play @marcospereira
• Follow the OpenShift Lagom guide @marcospereira
• Evaluate the impacts of Akka 2.6 in Play & Lagom @renatocaval
• Akka Projections @renatocaval & @marcospereira
  • Cluster distribution
  • Output is a presentation to Play/Lagom team (invite Akka team as well)
• JUnit 5 support

[TimMoore]

The changes around the Lagom example applications seem worth discussing more widely, both within Lightbend and in the community.

[dwijnand]

The changes around the Lagom example applications seem worth discussing more widely, both within Lightbend and in the community.

@TimMoore let's discuss that in #33. Both Ignasi and Renato hold some different opinions so let's agree on a plan there first. Renato has agreed to lay out his ideas there so Ignasi and others can discuss off of those.

[SethTisue]

My own main concern is that we not let Lightbend stuff lag too far behind in the JDK 8 community build.
I'm not super concerned about building on JDK 11, it's only a nice-to-have.

I can't recall if there is anything here that affects running published artifacts on JDK 11. If so, that's a potential issue for users and customers and probably means it should be a priority after all (not urgently, but not many months of back-burnering, either?).

[dwijnand]

I agree with the priority of not letting ssl-config -> play -> lagom lag, due to being forked in the community build. So I'll unbreak the situation by reverting the initial change.

I also agree with the less-important-but-still-important goal of getting it working on Java 11 (it's one of the current priorities: "Drop allow_failures for AdoptOpenJDK 11" above).

[TimMoore]

@TimMoore let's discuss that in #33.

Sounds good, but I still suggest making this issue/discussion more visible. I don't think all interested parties will necessarily be watching this repo.