optimizely · mikeproeng37 · Apr 11, 2018 · Apr 10, 2018 · Apr 10, 2018 · Apr 11, 2018
diff --git a/packages/optimizely-sdk/CHANGELOG.MD b/packages/optimizely-sdk/CHANGELOG.MD
@@ -1,3 +1,38 @@
+## 2.0.0
+April 11th, 2018
+
+This major release of the Optimizely SDK introduces APIs for Feature Management. It also introduces some breaking changes listed below.
+
+### New Features
+* Introduces the `isFeatureEnabled` API to determine whether to show a feature to a user or not.
+```
+var enabled = optimizelyClient.isFeatureEnabled('my_feature_key', 'user_1', userAttributes);
+```
+
+* You can also get all the enabled features for the user by calling the following method which returns a list of strings representing the feature keys:
+```
+var enabledFeatures = optimizelyClient.getEnabledFeatures('user_1', userAttributes);
+```
+
+* Introduces Feature Variables to configure or parameterize your feature. There are four variable types: `Integer`, `String`, `Double`, `Boolean`.
+```
+var stringVariable = optimizelyClient.getFeatureVariableString('my_feature_key', 'string_variable_key', 'user_1');
+var integerVariable = optimizelyClient.getFeatureVariableInteger('my_feature_key', 'integer_variable_key', 'user_1');
+var doubleVariable = optimizelyClient.getFeatureVariableDouble('my_feature_key', 'double_variable_key', 'user_1');
+var booleanVariable = optimizelyClient.getFeatureVariableBoolean('my_feature_key', 'boolean_variable_key', 'user_1');
+```
+
+### Breaking changes
+* The `track` API with revenue value as a stand-alone parameter has been removed. The revenue value should be passed in as an entry of the event tags map. The key for the revenue tag is `revenue` and will be treated by Optimizely as the key for analyzing revenue data in results.
+```
+var eventTags = {
+  'revenue': 1200
+};
+
+optimizelyClient.track('event_key', 'user_id', userAttributes, eventTags);
+```
+* The package name has changed from `optimizely-client-sdk` to `optimizely-sdk` as we have consolidated both Node and JavaScript SDKs into one.
+
 ## 2.0.0-beta1
 March 29th, 2018
 

diff --git a/packages/optimizely-sdk/README.md b/packages/optimizely-sdk/README.md
@@ -12,7 +12,7 @@ The SDK is available through [npm](https://npmjs.com/package/optimizely-sdk). To
 npm install @optimizely/optimizely-sdk --save
 ```
 
-Or to use in a non CommonJS fashion:
+Or to use in a non CommonJS fashion in the Browser:
 
 1. Run `npm run build`
 2. Pull in `dist/optimizely.browser.umd.min.js` as a `<script>`
@@ -28,6 +28,10 @@ This version represents a major version change and, as such, introduces some bre
 
 - You will no longer be able to pass in `revenue` value as a stand-alone argument to the `track` call. Instead you will need to pass it as an entry in the [`eventTags`](https://developers.optimizely.com/x/solutions/sdks/reference/index.html?language=javascript#event-tags).
 
+### Feature Management Access
+
+To access the Feature Management configuration in the Optimizely dashboard, please contact your Optimizely account executive.
+
 ### Using the SDK
 See the Optimizely X Full Stack testing [developer documentation](http://developers.optimizely.com/server/reference/index.html) to learn how to set up your first JavaScript project and use the SDK.
 

diff --git a/packages/optimizely-sdk/lib/utils/enums/index.js b/packages/optimizely-sdk/lib/utils/enums/index.js
@@ -128,9 +128,8 @@ exports.RESERVED_EVENT_KEYWORDS = {
 };
 
 exports.JAVASCRIPT_CLIENT_ENGINE = 'javascript-sdk';
-exports.NEW_OPTIMIZELY_VERSION = '2';
 exports.NODE_CLIENT_ENGINE = 'node-sdk';
-exports.NODE_CLIENT_VERSION = '2.0.0-beta1';
+exports.NODE_CLIENT_VERSION = '2.0.0';
 
 /*
  * Notification types for use with NotificationCenter

diff --git a/packages/optimizely-sdk/package.json b/packages/optimizely-sdk/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@optimizely/optimizely-sdk",
-  "version": "2.0.0-beta1",
+  "version": "2.0.0",
   "description": "JavaScript SDK package for Optimizely X Full Stack",
   "main": "dist/optimizely.node.js",
   "browser": "dist/optimizely.browser.cjs.js",