Sprint 111-113 Summary #17096

Open
jmarolf opened this Issue Feb 11, 2017 · 8 comments

Projects

None yet

6 participants

@jmarolf
Member
jmarolf commented Feb 11, 2017 edited

Note:

These last 3 sprints have essentially been:
image
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.

Sprint 111-113 Stats

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

VB/C# Compiler Team Accomplishments

  • Implemented
    • RTM bug fixes
    • discards
    • while-loop out-var scope changes
  • Testing
  • Dogfooding
    • Compiler features
    • VS 2017 in general
    • Found a number of bugs we’ll address post Release-to-Web
  • Triaging incoming Visual Studio feedback and reported crashes
  • Post RTM design work
    • Readonly ref proposal on csharplang
    • Infrastructure and planning for point releases

F# Team Accomplishments

image

  • Shipped the bits to VS 2017 RC4
  • Improvements to internal builds infrastructure
  • Announced our immediate 2017 roadmap

Interactive Execution Team Accomplishments

  • New Live-Unit-Testing functionality
    • Pause/Resume
    • Exclude single tests
  • Testing
  • Dogfooding, ourselves (any repo and solution we can get our hands on) and helping partner teams dogfood ( VSO repo, VS repo, Windows and Office)
  • Fixing RTM issues

Project & Analysis Team Accomplishments

  • New Project System Features
    • Transitive P2Ps
    • Package page
    • Publish page
  • Bug fixes
  • More bug fixes
  • Dogfooding

.NET CLI Team

  • CLI 1.0 Features
    • Migrate xproj/project.json to msbuild with dotnet migrate!!!!
      • Works even on large complex projects
    • Project creation with new templates dotnet new console
      • New templating engine
    • Create a new solution file dotnet new sln
    • Add projects to a solution dotnet sln add
    • Add new nuget package dependency with dotnet add package
    • Add new project reference with dotnet add reference

IDE Team Accomplishments

  • Releases

    • .editorconfig support for naming styles
    • Bug fixing and testing
      • A bunch of long-standing Watsons and important fixes to new features
    • Delivered a Dev14 hotfix for some customer impacting issues
  • Post-RTW

    • Refactoring: Convert if to switch (contributed by @alrz)
    • Refactoring: Change base or add digit separators to numeric literals (contributed by @alrz)
    • ~20 other bug fixes

Omnisharp

  • Shipped 1.7 release!
    • New TextMate grammar for syntax highlighting
    • Support for latest .NET Core .csproj projects
    • NuGet package restore for .csproj projects
    • Several improvements to Code Actions
@vbcodec
vbcodec commented Feb 11, 2017

will VS RTM be available to download before ship / release date ?

@vbcodec
vbcodec commented Feb 11, 2017 edited

what realy means "Infrastructure and planning for point releases" ?
Releasing of compilers independent from VS ? (similar to Typescript)

@jmarolf
Member
jmarolf commented Feb 11, 2017

@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
Contributor
alrz commented Feb 11, 2017 edited

#6543 and #16664 are not the same thing though. :)

@chrisaut

@alrz wrong thread?

@alrz
Contributor
alrz commented Feb 11, 2017

No, linked PR for the second refactoring in post-rtw doesn't seem to be correct.

@jmarolf
Member
jmarolf commented Feb 11, 2017

@alrz whoops sorry, I updated the summary (though I appreciate @Giftednewt 's contribution as well 😄 )

@Pilchie Pilchie added the Discussion label Feb 14, 2017
@Giftednewt
Contributor

@jmarolf Always glad to contribute 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment