These last 3 sprints have essentially been:

But we've recently had time to come up for air so I will attempt to summarize the work of the last 1.5 months.
| Repository | Bugs Closed| Pull Requests Merged |
|:-------------:|:-------------:|:-------------:|
| Roslyn | 608 | 545
| F#| 199 | 228
| Project System | 348 | 198
| .NET CLI | 553 | 228 |
| .NET SDK | 187 | 144 |
| Omnisharp | 14 | 35 |
| Total | 1909 | 1378 |

dotnet migrate!!!!dotnet new consoledotnet new slndotnet sln adddotnet add packagedotnet add referenceReleases
Post-RTW
Shipped 1.7 release!
will VS RTM be available to download before ship / release date ?
what realy means "Infrastructure and planning for point releases" ?
Releasing of compilers independent from VS ? (similar to Typescript)
@vbcodec every feature checked into the master branch made it into the latest public RC. Features checked into post-dev15 will likely not be in the initial version of Visual Studio 2017. Regarding point releases, its unclear exactly what we are going to do (we are still planning after all), but I believe that the LDM wants release independence like typescript. Frankly, this is something we will want feedback on regarding the right release cadence.
@alrz wrong thread?
No, linked PR for the second refactoring in post-rtw doesn't seem to be correct.
@alrz whoops sorry, I updated the summary (though I appreciate @Giftednewt 's contribution as well 馃槃 )
@jmarolf Always glad to contribute 馃槃
Most helpful comment
@vbcodec every feature checked into the master branch made it into the latest public RC. Features checked into post-dev15 will likely not be in the initial version of Visual Studio 2017. Regarding point releases, its unclear exactly what we are going to do (we are still planning after all), but I believe that the LDM wants release independence like typescript. Frankly, this is something we will want feedback on regarding the right release cadence.