Updates for GA release

Author: VesaJuvonen

.github/CONTRIBUTING.md

@@ -20,7 +20,7 @@ docs
 ```
 At this time, contributions are accepted for:
 
-* SharePoint Framework Developer Preview
+* SharePoint Framework
 * SharePoint Webhooks
 
 ### SPFx Folder

docs/apis/webhooks/get-started-webhooks.md

@@ -450,7 +450,7 @@ Now add a file to the Documents library and test if you get a notification from
 * Go to the **Documents** library. It will be named **Shared Documents** library in your default site collection.
 * Add a new file.
 * Go to Visual Studio and wait for the breakpoint to be hit.
-   * In preview, the wait time may vary from a few seconds up to five minutes. When the breakpoint is hit, the webhook receiver has just received a notification from SharePoint.
+   * Wait time may vary from a few seconds up to five minutes. When the breakpoint is hit, the webhook receiver has just received a notification from SharePoint.
 * Choose **F5** to continue.
 * To see the notification data, look in the **Output** window for the following entries, since you added the notification data into the trace log:
 

docs/spfx/roadmap.md

@@ -2,14 +2,13 @@
 
 First release of the SharePoint Framework will contain support for client-side web parts. This is however just a start on the journey for providing additional modern customization capabilities to SharePoint. This article lists the different areas which are in our backlog for the future releases of SharePoint Framework.
 
-> Notice. This is a list areas which SharePoint engineering is having in the backlog and are looking into. This does **NOT** mean that all of them will be necessarily delivered, but we are looking for getting items and topics from this list gradually released with the future releases of SharePoint Framework.  
+> Notice. This is a list of areas which SharePoint engineering is having in the backlog and are looking into. This does **NOT** mean that all of them will be necessarily delivered, but we are looking for getting items and topics from this list gradually released with the future releases of SharePoint Framework.  
 
 ## On-premises support
 
 - Shipping as part of Feature Pack 
 - Similar feature capabilities as in SharePoint Online
 - Target is to provide common development platform across on-premises and the cloud
-    - Getting head-start on your cloud migration
 - Leveraging modern toolchain and open source on “legacy” environments
 - Targeting SharePoint 2016 version during calendar year 2017
 
@@ -40,26 +39,16 @@ First release of the SharePoint Framework will contain support for client-side w
 - Streamlined approval experience: no need to know who your tenant admin is anymore
     - Owner initiate the approval process
     - Tenant admin gets automatically notified 
-    - Settings to control the default experience: 
-        - auto approve for a set of people (e.g. “trusted team”)
-        - approve or deny after XX days 
-
-- ALM REST APIs
-    - Deploy packages
-    - Activate the app
-    - Delete the app
-    - Upgrade the app
+    - Settings to control the default experience around approval process
 
+- ALM REST APIs - Deploy, activate, delete and upgrade apps and add-ins
 - ALM REST APIs targeted to support *everything* in the App Catalog, including add-ins
 - Automatic CDN hosting for code
     - Package JavaScript bundle into app package, which is automatically then deployed to a library that gets hosted on your tenant Office 365 CDN
 
 
 ## Developer Experience
-- SharePoint Framework Workbench 2.0: Development story beyond web parts
-    - "code parts", Apps and Pages support
-    - "Connect to SharePoint" for easy switching between local and online workbench
-
+- SharePoint Framework Workbench 2.0: Development story beyond web parts with support for new componen types on top of client-side web parts
 - Tool Chain Components
 - Additional Yeoman Templates
 
@@ -68,8 +57,6 @@ First release of the SharePoint Framework will contain support for client-side w
 - List level: custom view item, edit item, delete item, add item
 - Page level: assign an app to a page to a full custom page experience
 - Mobile
-    - Like everything in the framework: responsive OOB
-    - SharePoint Mobile app either launches an external app or responsive renders of the app
 
 ## Additional resources
 Please use following resources to stay up to date on the new releases and capabilities being released for SharePoint Framework.

docs/spfx/set-up-your-developer-tenant.md

@@ -1,7 +1,5 @@
 # Set up your Office 365 tenant
 
->**Note:** The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production environments.
-
 To build and deploy client-side web parts using the preview release of the SharePoint Framework, you will need an Office 365 tenant with [First Release](https://support.office.com/en-us/article/Set-up-the-Standard-or-First-Release-options-in-Office-365-3b3adfa4-1777-4ff0-b606-fb8732101f47) options enabled. 
 
 ## Sign up for an Office 365 tenant

docs/spfx/set-up-your-development-environment.md

@@ -1,7 +1,5 @@
 # Set up your SharePoint client-side web part development environment
 
->**Note:** The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production environments.
-
 You can use Visual Studio, or your own custom development environment to build SharePoint client-side web parts. You can use a Mac, PC, or Linux.
 
 >**Note:** Before following the steps in this article, be sure to [Set up your Office 365 Tenant](./set-up-your-developer-tenant).

docs/spfx/sharepoint-framework-overview.md

@@ -1,7 +1,5 @@
 # Overview of the SharePoint Framework
 
->**Note:** The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production environments.
-
 The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready from day one. The SharePoint Framework works for SharePoint on-premises and SharePoint Online.
 
 Key features of the SharePoint Framework include:

docs/spfx/team-based-development-on-sharepoint-framework.md

@@ -4,15 +4,14 @@ SharePoint Framework is a new development model for building SharePoint customiz
 
 SharePoint Framework is a development model, and despite the differences in the underlying technology, the same concepts apply when using it for building solutions, as to other development models SharePoint developers used in the past. Developers use the SharePoint Framework toolchain to build and test their solutions and once ready, they hand over the solution package to be deployed on the SharePoint tenant for further testing and release.
 
-SharePoint Framework consists of a few different packages. These packages, each in its own specific version, make up a release of the SharePoint Framework. For example the Release Candidate (RC0) of the SharePoint Framework consists of the following package versions:
-
-- @microsoft/sp-client-base v0.7.0
-- @microsoft/sp-client-preview v0.9.0
-- @microsoft/sp-core-library v0.1.2
-- @microsoft/sp-webpart-base v0.4.0
-- @microsoft/sp-build-web v0.9.0
-- @microsoft/sp-module-interfaces v0.7.0
-- @microsoft/sp-webpart-workbench v0.8.0
+SharePoint Framework consists of a few different packages. These packages, each in its own specific version, make up a release of the SharePoint Framework. For example the General Availability release of the SharePoint Framework consists of the following package versions:
+
+- @microsoft/sp-client-base v1.0.0
+- @microsoft/sp-core-library v1.0.0
+- @microsoft/sp-webpart-base v1.0.0
+- @microsoft/sp-build-web v1.0.0
+- @microsoft/sp-module-interfaces v1.0.0
+- @microsoft/sp-webpart-workbench v1.0.0
 
 For a project to target a specific release of the SharePoint Framework it has to reference all the different packages in the correct versions. When scaffolding new projects, the SharePoint Framework Yeoman generator automatically adds the necessary references to the package from the corresponding release of the SharePoint Framework. But when upgrading the project to a newer version of the SharePoint Framework developers have to pay extra attention to correctly update version numbers of the SharePoint Framework packages.
 

docs/spfx/toolchain/extending-webpack-in-build-pipeline.md

@@ -1,7 +1,5 @@
 # Extending webpack in the SharePoint Framework toolchain
 
->**Note:** The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production environments.
-
 [Webpack](https://webpack.github.io/) is a JavaScript module bundler that takes your JavaScript files and its dependencies and generates one or more JavaScript bundles so you can load different bundles for different scenarios.
 
 The framework tool chain uses CommonJS for bundling. This enables you to define modules and where you want to use them. The tool chain also uses SystemJS, a universal module loader, to load your modules. This helps you to scope your web parts by making sure that each web part is executed in its own namespace.

docs/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md

@@ -1,7 +1,5 @@
 # Integrate gulp tasks in SharePoint Framework toolchain
 
->**Note:** The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production environments.
-
 SharePoint client-side development tools use [gulp](http://gulpjs.com/) as the build process task runner to:
 
 * Bundle and minify JavaScript and CSS files.

docs/spfx/toolchain/sharepoint-framework-toolchain.md

@@ -1,7 +1,5 @@
 # SharePoint Framework Toolchain
 
->**Note:** The SharePoint Framework is currently in preview and is subject to change. SharePoint Framework client-side web parts are not currently supported for use in production environments.
-
 ## Overview
 The SharePoint Framework toolchain is the set of build tools, framework packages, and other items that manage building and deploying your client side projects. The toolchain helps you build client-side components like web parts. It also helps you test them in your local development environment with tools such as the SharePoint Workbench. And you can use the toolchain to package and deploy to SharePoint. The toolchain also provides you with a set of build commands that help you to complete key build tasks such as code compilation, packaging the client-side project into a SharePoint app package and more. 
 
@@ -19,8 +17,6 @@ The following packages are in the SharePoint Framework:
 
 * [@microsoft/sp-client-base](https://www.npmjs.com/package/@microsoft/sp-client-base) - Defines the core libraries for client-side applications built using the SharePoint Framework
 
-* [@microsoft/sp-client-preview](https://www.npmjs.com/package/@microsoft/sp-client-preview) - Contains SharePoint Framework libraries that are still under development. Once they are finalized, they will be refactored into separate npm packages.
-
 * [@microsoft/sp-webpart-workbench](https://www.npmjs.com/package/@microsoft/sp-webpart-workbench) - The SharePoint Workbench is a standalone environment for testing and debugging client-side web parts.
 
 * [@microsoft/sp-module-loader](https://www.npmjs.com/package/@microsoft/sp-module-loader) - A module loader that manages versioning and loading of client-side components, web parts, and other assets. It also provides basic diagnostic services. It is built on familiar standards such as SystemJS and WebPack, and is the first part of the SharePoint Framework to load on a page.
@@ -82,18 +78,22 @@ Below is the `package.json` of the [helloworld-webpart](web-parts/get-started/bu
     "node": ">=0.10.0"
   },
   "dependencies": {
-    "@microsoft/sp-client-base": "~0.1.12",
-    "@microsoft/sp-client-preview": "~0.1.12"
+    "@microsoft/sp-client-base": "~1.0.0",
+    "@microsoft/sp-core-library": "~1.0.0",
+    "@microsoft/sp-webpart-base": "~1.0.0",
+    "@types/webpack-env": ">=1.12.1 <1.14.0"
   },
   "devDependencies": {
-    "@microsoft/sp-build-web": "~0.4.32",
-    "@microsoft/sp-module-interfaces": "~0.1.8",
-    "@microsoft/sp-webpart-workbench": "~0.1.12",
-    "gulp": "~3.9.1"
+    "@microsoft/sp-build-web": "~1.0.0",
+    "@microsoft/sp-module-interfaces": "~1.0.0",
+    "@microsoft/sp-webpart-workbench": "~1.0.0",
+    "gulp": "~3.9.1",
+    "@types/chai": ">=3.4.34 <3.6.0",
+    "@types/mocha": ">=2.2.33 <2.6.0"
   },
   "scripts": {
     "build": "gulp bundle",
-    "clean": "gulp nuke",
+    "clean": "gulp clean",
     "test": "gulp test"
   }
 }