Skip to content

add headers to blog post #903

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

Merged
merged 1 commit into from
Jun 6, 2018
Merged

add headers to blog post #903

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
12 changes: 10 additions & 2 deletions _posts/2018-06-05-collections-feature-freeze.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,15 @@ by: Stefan Zeiger
title: Scala 2.13 Collections Feature Freeze
---

## How's 2.13 coming?

[Scala 2.13.0-M4](https://www.scala-lang.org/news/2.13.0-M4) was released two weeks ago and we are now heading towards the final milestone before RC1. The planned release date for [Scala 2.13.0-M5](https://github.com/scala/scala/milestone/74) is August 10. This constitutes the general feature freeze for the 2.13 compiler and library.

For the collections library in particular the feature freeze will already happen on June 22 (after Scala Days New York). Collections were [redesigned from scratch](https://www.scala-lang.org/blog/2017/02/28/collections-rework.html) for 2.13, therefore we are allocating more time for bug fixes and improved backwards compatibility after the feature freeze.
## Collections feature freeze: June 22

For the collections library in particular the feature freeze will already happen on June 22 (after Scala Days New York). Collections were [redesigned from scratch](https://www.scala-lang.org/blog/2017/02/28/collections-rework.html) for 2.13, therefore we are allocating more time for bug fixes and improved backwards compatibility after the feature freeze.

## Remaining goals

The most important goals now are reaching stability and feature parity with the 2.12 library (except where we deliberately drop features). Changes to restore missing features from 2.12 will still be accepted but new features (like additional collection types or convenience methods) will not. Even before the deadline we take a conservative approach to new methods and collection types in order to avoid scope creep.

Expand All @@ -16,4 +22,6 @@ Another area with a lot of ongoing work is documentation, in particular scaladoc

Note that [binary compatibility](https://docs.scala-lang.org/overviews/core/binary-compatibility-of-scala-releases.html), both backwards and forwards, is required for all official Scala minor releases and also expected for release candidates. Breaking binary compatibility is still possible between M5 and RC1 but new features that miss the feature freeze deadline will have to target Scala 2.14 instead.

Adoption of Scala 2.13.0-M4 so far has been slower than for most milestones because the number of source incompatibilities is higher than usual. We hope that an early feature freeze and further compatibility improvements will make it easier for core projects to upgrade to M5 (whether they are already on M4 or not) in order to bootstrap the Scala ecosystem in preparation for the 2.13.0 release.
## Ecosystem update

Adoption of Scala 2.13.0-M4 so far has been slower than for most milestones because the number of source incompatibilities is higher than usual. We hope that an early feature freeze and further compatibility improvements will make it easier for core projects to upgrade to M5 (whether they are already on M4 or not) in order to bootstrap the Scala ecosystem in preparation for the 2.13.0 release.