Hi,
It's been a long year, but we are getting close to the next Scala IDE major release, planned for the end of this month. Before we uncork the champaign, we need a short administrative detour:
As usual, we want to slow down and only fix important bugs, while reducing the risk of introducing regressions. To that end, we are going to branch off a 3.0.x branch today, on what we'll ultimately base the release. 'master' continues to live as the development branch for our next release (Lithium).
What does it mean for you? Nothing much changes: new pull requests should target `master`, just like before. If you think the fix is safe and essential to be included in the release, please mention in the message that you'd like to backport it to the 3.0.x release. Once the PR is merged, please open another PR with [backport] in the title, cherry-picking your commits.
The 'master' branch will not require 2.9.x compatibility! Until we fix our automatic build bots, there might be reports about builds with 2.9 as well, but they can be ignored.
One last thing: the `platform/juno` branch will continue to merge with the 3.0.x branch. We will not branch `platform/juno`, since right after the release we will merge master and Juno, making Juno the default supported platform for the upcoming release.
There are a number of pull requests in the queue right now, so in order to minimize the backporting effort, it would be good to review and merge them to master *before* branching. I'll branch on Monday morning (CET), Feb 4th, so please keep an eye on the PR queue.
cheers,
iulian
--
« Je déteste la montagne, ça cache le paysage »
Alphonse Allais