chore: Preparing for 3.3.0 release (#215)

Author: aliabbasrizvi

CHANGELOG.md

@@ -1,5 +1,16 @@
 # Optimizely Python SDK Changelog
 
+## 3.3.0
+October 25th, 2019
+
+### New Features:
+* Added support for event batching via the event processor.
+  * Events generated by methods like `activate`, `track`, and `is_feature_enabled` will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be batched into a single payload and sent to the event dispatcher.
+  * To configure event batching, set the `batch_size` and `flush_interval` properties when initializing instance of [BatchEventProcessor](https://github.com/optimizely/python-sdk/blob/3.3.x/optimizely/event/event_processor.py#L45).
+  * Event batching is disabled by default. You can pass in instance of `BatchEventProcessor` when creating `Optimizely` instance to enable event batching.
+  * Users can subscribe to `LogEvent` notification to be notified of whenever a payload consisting of a batch of user events is handed off to the event dispatcher to send to Optimizely's backend.
+* Introduced blocking timeout in `PollingConfigManager`. By default, calls to `get_config` will block for maximum of 10 seconds until config is available. 
+
 ## 3.2.0
 August 27th, 2019
 

optimizely/version.py

@@ -11,5 +11,5 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-version_info = (3, 2, 0)
+version_info = (3, 3, 0)
 __version__ = '.'.join(str(v) for v in version_info)