Release 0.1.5

mozilla-lockwise · Jan 29, 2018 · c3c31d3 · c3c31d3
1 parent 19a0c05
commit c3c31d3
Show file tree

Hide file tree

Showing 101 changed files with 6,063 additions and 3,027 deletions.
diff --git a/.travis.yml b/.travis.yml
@@ -5,6 +5,7 @@ _aliases:
     language: node_js
     node_js: stable
 
+sudo: required
 jobs:
   include:
     - stage:

diff --git a/docs/contributing.md b/docs/contributing.md
@@ -14,13 +14,13 @@ Please refer to installation and build instructions in the [install documentatio
 
 ## How to Report Bugs
 
-Please open [a new issue in the GitHub repository](https://github.com/mozilla-lockbox/lockbox-extension/issues/new) with steps to reproduce the problem you're experiencing.
+Please open [a new issue in the appropriate GitHub repository](https://github.com/mozilla-lockbox/lockbox-extension/issues/new) with steps to reproduce the problem you're experiencing.
 
 Be sure to include as much information including screenshots, text output, and both your expected and actual results.
 
 ## How to Request Enhancements
 
-First, please refer to the applicable [GitHub project](https://github.com/orgs/mozilla-lockbox/projects) and search [the repository's GitHub issues](https://github.com/mozilla-lockbox/lockbox-extension/issues) to make sure your idea has not been (or is not still) considered.
+First, please refer to the applicable [GitHub repository](https://github.com/orgs/mozilla-lockbox/) and search [the repository's GitHub issues](https://github.com/mozilla-lockbox/lockbox-extension/issues) to make sure your idea has not been (or is not still) considered. It may also be easier to see and search across all projects combined on our [Waffle.io planning board](https://waffle.io/mozilla-lockbox/lockbox-extension).
 
 Then, please [create a new issue in the GitHub repository](https://github.com/mozilla-lockbox/lockbox-extension/issues/new) describing your enhancement.
 

diff --git a/docs/css/extra.css b/docs/css/extra.css
@@ -26,5 +26,5 @@ div.right {
 }
 
 .rst-content .admonition-title::before {
-    display: none; !important
+  display: none !important;
 }
diff --git a/docs/index.md b/docs/index.md
@@ -19,7 +19,7 @@ security.
 
 Install it and sign in with your Firefox Account to encrypt your data with
 tamper-resistant block cipher technology. Then [share feedback
-here](feedback-link).
+here][feedback-link].
 
 ## Get Started
 

diff --git a/docs/release-notes.md b/docs/release-notes.md
@@ -1,8 +1,35 @@
 # Lockbox Release Notes
 
+## 0.1.5-alpha
+
+_Date: 2018-01-30_
+
+### What's New
+
+* There is a version query param to the SurveyGizmo link for better feedback tracking ([#388](https://github.com/mozilla-lockbox/lockbox-extension/issues/388))
+* We're now using greenkeeper to help keep up dependencies ([#276](https://github.com/mozilla-lockbox/lockbox-extension/issues/276))
+
+### What's Fixed
+
+* Addressed a syntax error causing warnings in the build around the prop type:ScrollingList ([#451](https://github.com/mozilla-lockbox/lockbox-extension/issues/451))
+* Clicking "New entry" button while editing an entry no longer duplicates the entry ([#438](https://github.com/mozilla-lockbox/lockbox-extension/issues/438))
+* Added stylelint CSS linter to better catch programming errors ([#352](https://github.com/mozilla-lockbox/lockbox-extension/issues/352))
+* The `expires_at` value during FxA login is now valid ([#430](https://github.com/mozilla-lockbox/lockbox-extension/issues/430))
+* The "guest mode" key is now defined in the extension and not the shared datastore module ([#435](https://github.com/mozilla-lockbox/lockbox-extension/issues/435))
+* There is no longer an odd blue background when selecting items from left side list ([#414](https://github.com/mozilla-lockbox/lockbox-extension/issues/414))
+
+
+### Known Issues
+
+* Once you link a Firefox Account to Lockbox, you cannot unlink it from that account.
+* Once you link a Firefox Account to Lockbox, signing in with a different account can render Lockbox unusable until you quit and restart Firefox.
+* Once you link a Firefox Account to Lockbox, resetting your Firefox Account password through "forgot your password" will render all your logins inaccessible; the only recourse is to reset Lockbox and start over.
+* Firefox's default prompt to save logins is only disabled on new installs of this extension; updating Lockbox will not change your current Firefox preferences.
+
+
 ## 0.1.4-alpha
 
-_Date: 2017-12-11_
+_Date: 2017-12-13_
 
 ### What's New
 
@@ -12,9 +39,6 @@ _Date: 2017-12-11_
 - Get help and instructions when you first get started ([#392](https://github.com/mozilla-lockbox/lockbox-extension/issues/392))
 - Get additional support from the updated [Lockbox website](https://mozilla-lockbox.github.io/lockbox-extension/), including the FAQ ([#345](https://github.com/mozilla-lockbox/lockbox-extension/issues/345))
 
-
-### What's Fixed
-
 ### Known Issues
 
 * **Any existing Lockbox entries from previous versions have been removed.** Previous versions were storing and encrypting data differently than we are now. In order to add our new security features your old data can no longer be read/accessed and you'll see an empty state after you upgrade.

diff --git a/docs/releases.md b/docs/releases.md
@@ -30,26 +30,22 @@ To generate the next release binary:
     - each release includes the sub headings "What's New", "What's Fixed", and "Known Issues"
     - consult with Product Management on wording if needed
 2. Commit and ultimately merge to `master` branch
-3. Merge the `master` branch into `production` branch and push to GitHub:
-    - `git checkout master`
-    - `git pull upstream master` (to make sure you have the latest)
-    - `git checkout production`
-    - `git pull upstream production` (to make sure you have the latest)
-    - `git merge master`
-    - `git push upstream production`
-    - Test Pilot's Jenkins will now build and sign the extension (see ["Extension Signing"](#extension-signing))
+3. Create a pull request on GitHub [comparing changes from the `master` branch against/to `production`][production-compare]
+    - Open the pull request so we can show the changes, CI status, and approvals
+      - Request an approval from the P.I. and Product representatives
+    - Once the release has been reviewed, tested, and approved to go live, merge and close the pull request
+    - Test Pilot's Jenkins will then build, sign, and deploy the extension (see ["Extension Signing"](#extension-signing))
 4. Tag the latest commit on `production` branch with an annotated version and push the tag:
     - `git tag -a -m "Release 0.1.0" 0.1.0`
     - `git push upstream 0.1.0`
-    - Travis-CI will build and generate a GitHub Release
+    - Travis-CI will build and generate a [GitHub Release][releases]
 7. Edit the resulting GitHub Release
-    - Set the GitHub Release title to match the version
+    - Set the [GitHub Release][releases] title to match the version
     - Set the GitHub Release notes to match the `docs/release-notes.md`
     - Download the signed add-on: `wget -O signed-addon.xpi https://testpilot.firefox.com/files/lockbox@mozilla.com/latest`
     - Attach to the GitHub Release the downloaded signed add-on
 8. Send an announcement to the team (e.g., via Slack team channel)
 
-
 ## Extension Signing
 
 Learn about the Test Pilot extension deployment and hosting process here:  
@@ -65,3 +61,6 @@ The resulting files deployed are:
 - Latest version of the signed extension XPI: [https://testpilot.firefox.com/files/lockbox@mozilla.com/latest](https://testpilot.firefox.com/files/lockbox@mozilla.com/latest)
 
 **IMPORTANT:** Test Pilot reports the status of build, signing, and deployment of its artifacts on the IRC channel **#testpilot-bots**.  Be sure to join the channel prior to pushing the `production` branch to GitHub in order to receive the status updates.
+
+[production-compare]: https://github.com/mozilla-lockbox/lockbox-extension/compare/production...master
+[releases]: https://github.com/mozilla-lockbox/lockbox-extension/releases
diff --git a/docs/telemetry-test-plan.md b/docs/telemetry-test-plan.md
@@ -0,0 +1,19 @@
+# Telemetry Test Plan: Lockbox-extension
+
+Given the importance the Lockbox team places on actionable user telemetry, ensuring confidence in the fidelity of that data is vital. Coverage aspects are broken into two distinct areas: test automation and manual testing.
+
+## Unit tests
+When a new feature is developed or an additional user action needs to be recorded, the developer implementing the new telemetry event will add a unit test to ensure the action creates a ping.
+
+## Manual tests
+### New telemetry events
+Once a new telemetry event is added to a feature and that event has a unit test, the telemetry ping will be manually inspected by either Leif Oines, Product Data Scientist or Product Integrity. The goal of this exercise it to ensure the new event and accompanying unit test are capturing the correct user behavior.
+
+### Regression testing
+A small handful of smoke tests will manually be run prior to each release. Note, the team will rely on the underlying unit tests for comprehensive testing of event verification.
+
+Product Integrity will investigate options for automating these tests into the integration test suite. 
+
+## Metrics being gathered
+
+For a comprehensive list of metrics being gathered review the [Lockbox Telemetry Plan](https://github.com/mozilla-lockbox/lockbox-extension/blob/telemetry_leif/docs/metrics.md#list-of-events-currently-recorded).
diff --git a/karma.conf.js b/karma.conf.js
@@ -16,11 +16,11 @@ module.exports = function(config) {
 
     basePath: "",
     files: [
-      "test/index.js",
+      "test/unit/index.js",
     ],
     exclude: [],
     preprocessors: {
-      "test/index.js": ["webpack", "sourcemap"],
+      "test/unit/index.js": ["webpack", "sourcemap"],
     },
 
     frameworks: ["mocha"],