Add proposed blog article for the new VSCode extension

Author: timsneath

_data/authors.yml

@@ -476,3 +476,7 @@ owen-voorhees:
   name: Owen Voorhees
   github: owenv
   about: "Owen Voorhees is a member of the team at Apple working on Swift Build."
+
+adam-ward:
+  name: Adam Ward
+  about: "Adam Ward is a member of the team at Apple working on Swift tooling."

_posts/2025-02-10-vscode-swift-2.md

@@ -0,0 +1,17 @@
+---
+layout: post
+published: true
+date: 2025-02-10 14:00:00
+title: Updating the Visual Studio Code extension for Swift
+author: [adam-ward]
+---
+
+Today, we are excited to announce a new version of the Swift extension for Visual Studio Code -- now published to the extension marketplace as an official supported release of the Swift team. The aim of this extension is to provide a first-class, feature-complete extension that makes developing Swift applications on all platforms a seamless experience.
+
+![VS Code running with the Swift extension](/assets/images/vscode-extension-blog/vscode-swift-2.png)
+
+As we continue to invest in Swift as a first-class language for cross-platform development, both Apple and the broader developer community are rapidly iterating on the VSCode extension to expand its capabilities for server and cloud, embedded, and Linux and Windows app development. The original extension was developed by members of the Swift Server Working Group, and with its broader scope, they have graciously supported this transition to the GitHub /swiftlang organization and the creation of a new publisher for the extension.
+
+For existing Swift developers using VSCode, the transition should be seamless: the old release should automatically install the new extension and disable itself, and moving forward all language features will be provided by the new extension. You’re welcome to uninstall the original extension, which will be renamed to reflect its deprecated status. 
+
+Further details about the migration can be found on the Swift Forums. If you have any issues migrating, pleasefile an issue or comment on the forum post.