Please deploy autopush 1.3.0 to stage

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: benbangert, Assigned: oremj)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
autopush 1.3.0 is ready for staging. This release add's a new dynamodb table, the 'message' table.

1.3.0 (**dev**)
===============

Features
--------

* Add WebPush TTL scheme per spec (as of July 28th 2015). Issue #56.
* Add WebPush style data delivery with crypto headers to connected clients.
  Each message is stored independently in a new message table, with the version
  and channel id still required to ack a message. The version is a UUID4 hex
  which is also echo'd back to the AppServer as a Location URL per the current
  WebPush spec (as of July 28th 2015). Issue #57.
* Add Sphinx docs with ReadTheDocs publishing. Issue #98.
  This change also includes a slight Metrics refactoring with a IMetrics
  interface, and renames MetricSink -> SinkMetrics for naming consistency.

Bug Fixes
---------

* Increase test coverage of utils for 100% test coverage.
* Move all dependencies into requirements.txt and freeze them all explicitly.

Backward Incompatibilities
--------------------------

* ``bridge`` option is now ``external_router``.
(Assignee)

Updated

3 years ago
Assignee: nobody → oremj
(Reporter)

Comment 1

3 years ago
Forgot to mention, this version also supports a max_connections option, which we should set realistically on the stage cluster based on memory available. We'll also need to add this setting for production deployment to ensure nodes don't fall over under load when dropping excess connections.
(Assignee)

Comment 2

3 years ago
1.3.0 has been pushed to stage.
(Assignee)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.