Microsoft recently hosted the 3rd annual ALM Summit,
a gathering of Application Lifecycle Management (ALM) practitioners
interested in learning more about the craft and sharing their own
experiences with others. Over the course of three packed days and
across four tracks of discussions focused on DevOps, testing, agile
development, and ALM leadership, attendees are discussing and
collaborating with others in the field, all with the goal of improving
how our industry delivers software and services.
A key set of themes during this summit focuses on real change happening in the industry. In a world of devices and services, we’re seeing that feedback and iteration are the name of the game, with multi-year release trains replaced by faster and thoughtful build/measure/learn cycles, with a need for friction-free paths to production yielding advances in quality enablement and continuous deployment, with the blurring of development team roles, and with teams becoming more and more distributed.
All of this has led us to shift our approach in how we improve and release Visual Studio, while at the same time ensuring that new value includes capabilities to propel this “new normal.” In November, we shipped Visual Studio 2012 Update 1 (VS2012.1), an update to Visual Studio 2012 that provided not only fixes for bugs in the RTM release of Visual Studio 2012, but also a wealth of new features, spanning improved support for agile teams and continuous quality in addition to improved support for Windows and SharePoint development. Today, I’m happy to share that we’ve released our first preview of Visual Studio 2012 Update 2 (VS2012.2). This preview includes all of the improvements from VS2012.1 while also introducing web-based support for Test Case Management (TCM), improved support for work item tagging, unit testing features for Windows Phone 8, and more. You can now download this preview, and you can expect subsequent previews and the eventual release of VS2012.2 to contain many more exciting capabilities.
However, while I’m excited by this VS2012.2 preview release, I’m even more excited by another of today’s announcements. As Brian Harry just announced in his keynote this morning at the ALM Summit, we’ve added Git source code management to Team Foundation Service, with Git repositories hosted in Team Foundation Service available today for use seamlessly from any Git tool on any operating system. Developers can now benefit from Microsoft’s fully-integrated ALM suite, while at the same time having a choice of using Git or TFVC (Team Foundation Version Control) for their source control repositories. We’ll continue to invest in both Git and TFVC (Team Foundation Version Control) throughout future releases, as we see both centralized version control and distributed version control systems as being optimized for different types of projects and development workflows.
As part of this effort, today we’re also releasing a preview of an extension for VS2012.2 that enables connecting Visual Studio to Git repositories hosted in any Git host, including Team Foundation Service, CodePlex, GitHub, and any number of other 3rd-party services. To create this extension, we utilized the open source library libgit2, and in the process, several of our full-time engineers worked as committers to the libgit2 project. These capabilities will be built into a future release of Visual Studio, enabling it to serve as an incredibly robust Git client, one that provides seamless integration with the rest of the simplicity and power provided by Visual Studio.
A key set of themes during this summit focuses on real change happening in the industry. In a world of devices and services, we’re seeing that feedback and iteration are the name of the game, with multi-year release trains replaced by faster and thoughtful build/measure/learn cycles, with a need for friction-free paths to production yielding advances in quality enablement and continuous deployment, with the blurring of development team roles, and with teams becoming more and more distributed.
All of this has led us to shift our approach in how we improve and release Visual Studio, while at the same time ensuring that new value includes capabilities to propel this “new normal.” In November, we shipped Visual Studio 2012 Update 1 (VS2012.1), an update to Visual Studio 2012 that provided not only fixes for bugs in the RTM release of Visual Studio 2012, but also a wealth of new features, spanning improved support for agile teams and continuous quality in addition to improved support for Windows and SharePoint development. Today, I’m happy to share that we’ve released our first preview of Visual Studio 2012 Update 2 (VS2012.2). This preview includes all of the improvements from VS2012.1 while also introducing web-based support for Test Case Management (TCM), improved support for work item tagging, unit testing features for Windows Phone 8, and more. You can now download this preview, and you can expect subsequent previews and the eventual release of VS2012.2 to contain many more exciting capabilities.
However, while I’m excited by this VS2012.2 preview release, I’m even more excited by another of today’s announcements. As Brian Harry just announced in his keynote this morning at the ALM Summit, we’ve added Git source code management to Team Foundation Service, with Git repositories hosted in Team Foundation Service available today for use seamlessly from any Git tool on any operating system. Developers can now benefit from Microsoft’s fully-integrated ALM suite, while at the same time having a choice of using Git or TFVC (Team Foundation Version Control) for their source control repositories. We’ll continue to invest in both Git and TFVC (Team Foundation Version Control) throughout future releases, as we see both centralized version control and distributed version control systems as being optimized for different types of projects and development workflows.
As part of this effort, today we’re also releasing a preview of an extension for VS2012.2 that enables connecting Visual Studio to Git repositories hosted in any Git host, including Team Foundation Service, CodePlex, GitHub, and any number of other 3rd-party services. To create this extension, we utilized the open source library libgit2, and in the process, several of our full-time engineers worked as committers to the libgit2 project. These capabilities will be built into a future release of Visual Studio, enabling it to serve as an incredibly robust Git client, one that provides seamless integration with the rest of the simplicity and power provided by Visual Studio.
That needs to grow in a decent manner so that we can get to have a better productivity and in the same way agile business is what that has a good value with all the terms of growth and that is the way how it works.
ReplyDelete