|
1 | 1 | ---
|
2 | 2 | layout: blog-detail
|
3 | 3 | post-type: blog
|
4 |
| -by: The Scala organisation |
| 4 | +by: The Scala Center team, and community contributors |
5 | 5 | title: Scala 3 - Crossing the finish line
|
6 | 6 | ---
|
7 | 7 | ## Scala 3: Crossing the finish line
|
8 | 8 |
|
9 | 9 | #### Buckle up, we are a couple of days away from the Scala 3 Developer’s Preview!
|
10 | 10 |
|
11 |
| -As of 18th December we invite the community (users, contributors, maintainers, library authors, users, companies) to give one last big push of feedback to help the Scala org. cross the finish line. |
| 11 | +As of 18th December we invite the community (users, contributors, maintainers, library authors, users, companies) to give one last big push of feedback to help the teams working on the Scala 3 release cross the finish line. |
12 | 12 |
|
13 | 13 | After 8 years of developing Dotty, numerous feedback loops, and improvements, we are entering a “photo finish” phase, transforming Dotty to Scala 3.
|
14 | 14 |
|
@@ -49,14 +49,13 @@ The following sections will follow the previous update on Scala 3 release effort
|
49 | 49 | * acknowledge the questions that were raised,
|
50 | 50 | * describe the process we see ahead of us,
|
51 | 51 | * share decisions that we worked on,
|
52 |
| -* help us at the Scala organisation easier followup with our communication on different channels, |
| 52 | +* help us followup easier with our communication on different channels, |
53 | 53 |
|
54 | 54 | but not necessarily give all the answers, mostly because we can’t predict with certainty how things will play out. This is why we need you to continue this exciting journey with us to discover and create the new chapter, and we promise we would be as attentive and responsive as possible.
|
55 | 55 |
|
56 | 56 | #### What is “Developer’s Preview”?
|
57 | 57 |
|
58 |
| -The Scala organisation, in consultation with community partners and contributors, decided to allow some more time for adjustments before cutting the final Scala 3-RC1, originally scheduled for end of this year. |
59 |
| - |
| 58 | +In consultation with community partners and contributors, decided to allow some more time for adjustments before cutting the final Scala 3-RC1, originally scheduled for end of this year. |
60 | 59 |
|
61 | 60 | We will release Scala 3-M3 as a “Developer’s Preview”. Over the coming month, we will invite feedback from developers while striving to keep the API unchanged. If no major problem is raised between 18th Dec 2020 and mid Jan 2021 we will proceed to release RC1, aiming the end of January 2021, with the same API.
|
62 | 61 |
|
@@ -94,4 +93,4 @@ Starting from 3.T, versions will evolve in a similar way as before, with frequen
|
94 | 93 | Eventually, a new era will come, and we will have to break TASTy compatibility to move forward. That is when Scala 4 would come. Our goal is for that to happen at least 10 years from now.
|
95 | 94 |
|
96 | 95 | #### Where to next?
|
97 |
| -For the Scala organisation our priority in the next month is to collect, analyze, and respond to the feedback we get from you through the [Scala 3 Developer’s Preview satisfaction survey](https://docs.google.com/forms/d/e/1FAIpQLSflVmTu9lhrtnSTh2tKAjUGrt3WvEgwlDqZg66O3EVSXd1aJg/viewform?usp=sf_link) as well as from different other platforms you may choose to share your input. We thank you again for taking your time and helping Scala advance. |
| 96 | +Our priority in the next month is to collect, analyze, and respond to the feedback we get from you through the [Scala 3 Developer’s Preview satisfaction survey](https://docs.google.com/forms/d/e/1FAIpQLSflVmTu9lhrtnSTh2tKAjUGrt3WvEgwlDqZg66O3EVSXd1aJg/viewform?usp=sf_link) as well as from different other platforms you may choose to share your input. We thank you again for taking your time and helping Scala advance. |
0 commit comments