Release 0.1.2-alpha (#320)

* Use rjsx-mode for JS files in src/webextension

* Add placeholder for empty list

* Pre-release notes to include and push in 0.1.1-alpha1 (#279)

* Bump to version 0.1.1-alpha

* Add obvious warnings for repository and docs

* Add release notes to explain the pre-release warning

* Consistent strong treatment for pre-release warning

* Add a warning to first run introduction about this being a pre-release (#275)

* Add a warning to first run introduction
Fixes #270 requested by @sandysage  to explain features may change and data may not be retained between releases

* missing a word

* Better semantics for important message

* Clearer warning, doesn't bury lede, not as scary

* Quick hack to get strong tag output after localization happens

* Add release instructions (#158)

* Add instructions on how to prepare a new release

* forgot to remove old instructions when re-arranging

* include versioning notes, we follow semver

* add changelog convention and manual check step

* update releases.md based on conversations/reviews

* update changelog/release-notes section to reflect current realities

* reformat to account for mkdocs sublist handling

* updates based on personal experience

* expanding the last step into two

* (WIP) account for checklists

* cleanup and wording based on talks with @m8ttyB and @sandysage

* added line to releases.md about user stories/epics

* tweask to  section

* fix a typo

* Make `nsp` a dev-dependency so it can be run locally (and so we're not just assuming Travis will always have nsp installed)

* Update dependencies to all the latest versions

* Remove usage of withLocalization()/getString() from a few places

* Restore focus after closing modals

This partially resolves #133

* Fix unset classNames in <Toolbar/> and <ToolbarSpace/>; resolves #288

* Replace PNG of Lockie with transparent SVG

* Update editor tab URL when toolbar clicked (#278)



Fixes #262

This fix changes the URL for the tab assigned to the Editor (or
First-Time) is to be displayed.  This change does not:

* mess with the tab's history (`back`/`forward` buttons)
* keep whatever the user was originally navigated to

* open a new tab instead of resetting the current one

* remove extraneous newline

* Remove ASCII Lockie from welcome screen and replace with latest UI (#300)

* Replace PNG of Lockie with transparent SVG

* remove Lockie ASCII art

...at least, from the public's view 😏

* remove speech bubble and add SVG monster

* remove Lockie from copy

that's fun to say

* quick copy changes to match comps, not perfect still placeholder

* remove Lockie ASCII art

...at least, from the public's view 😏

* remove speech bubble and add SVG monster

* remove Lockie from copy

that's fun to say

* quick copy changes to match comps, not perfect still placeholder

* remove raw-loader

* re-work home page to have a title with entry counts

* address lint and test issues

* combine reused styles

* update background colors while I'm in here

* add alt tag for decorative images

https://www.w3.org/WAI/tutorials/images/decorative/

* combine titles and remove withLocalization

* tidy up CSS

* Add locked favicon to firstrun page

* Use Photon styling for buttons; resolves #265

* Use photon styling for inputs; resolves #256

* Remove browser-styles and tweak styles/colors to better match Photon

* Add dir-locals to test/ so that we get rjsx mode there!

* Address review comments

* Update to the latest photon spec for inputs

* Use Photon fonts; resolves #255

* Remove left margin from <FieldText/> and <LabelText/>

This matches the Photon spec more closely, but it might look weird...

* Let entry fields be selectable by the user

* Fix bad translation of item summary username

* Update icon to latest version and change color in context (#306)

provided by @changecourse

* Prepare 0.1.2-alpha (#305)

* Bump version 0.1.2-alpha
* Draft release notes
* Change homepage to point to GitHub Pages
* Add rest of items part of this release and fix links

* Set text area focus blue to match input styles (#328)

* Set text area focus blue to match input styles
* also update box-shadow for consistency

.travis.yml

@@ -8,7 +8,7 @@ addons:
 
 script:
   - STRICT_LINT=1 npm run test
-  - npx nsp check
+  - npm run nsp
 
 after_success:
   - npm run codecov

docs/release-notes.md

@@ -1,5 +1,28 @@
 # Lockbox Release Notes
 
+## 0.1.2-alpha
+
+_Date: 2017-11-13_
+
+### What's New
+
+* Interface styles updated to more closely match Photon design language ([#295](https://github.com/mozilla-lockbox/lockbox-extension/pull/295)) ([#307](https://github.com/mozilla-lockbox/lockbox-extension/pull/307))
+* Improved user interface design on welcome screen and home page ([#300](https://github.com/mozilla-lockbox/lockbox-extension/issues/300))
+* Updated content throughout the interface to guide the user experience ([#165](https://github.com/mozilla-lockbox/lockbox-extension/issues/165))
+
+### What's Fixed
+
+* Clicking the toolbar (browser action) icon would not open the editor if the editor was opened and the user changed the URL ([#262](https://github.com/mozilla-lockbox/lockbox-extension/issues/262))
+* The toolbar icon did not invert to light colors on dark themes ([#306](https://github.com/mozilla-lockbox/lockbox-extension/pull/306))
+
+### Known Issues
+
+* This is pre-release software subject to change. Your data may not be retained.
+* There is no way to change your Lockbox master password. If you forget your master password, you'll need to start over fresh by either:
+  - Opening the this extension's Preferences and clicking the "`💥💣 Reset 💣💥`" button; or
+  - Uninstalling and re-installing the extension
+* 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.1-alpha1
 
 _Date: 2017-11-01_

docs/releases.md

@@ -1,23 +1,67 @@
-## Releases
+# Releases
 
-## Preparation
+## Checklist
 
-To **prepare the extension for a new version**, you must:
+Before a release can be made, the following must be done:
 
-- update and commit the version in `package.json`
-- update and commit the `CHANGELOG.md`
-- tag, push, and merge to the `master` branch on GitHub
+* Any user stories labeled as `epic` to be included in the release are approved by Product and PI
+* All finished work is verified to work as expected and committed to `master`
+* Any unfinished work has been triaged and assigned to the appropriate milestone
+* Product, Engineering, and PI have voiced approval to release (e.g., via Slack team channel)
 
-## Packaging
 
-To **build a signed extension .xpi**, you must: commit and push to the
-`production` branch (ideally as a merge commit from `master`) on GitHub.
+## Instructions
+
+**NOTE:** these instructions assume:
+
+* All of the [checklist items](#checklist) are complete
+* You are an administrator of the project `lockbox-extension`
+* Your local git working copy has a remote named `upstream` pointing to `[email protected]:mozilla-lockbox/lockbox-extension.git`
+
+To generate the next release binary:
+
+1. Update "version" in package.json (and package-lock.json)
+    - we follow the [semver](http://semver.org/) syntax
+    - _Alpha_ releases will be labeled with "-alpha" (e.g., "0.1.0-alpha")
+    - _Beta_ releases will be labeled with "-beta" (e.g., "1.0.0-beta")
+    - _Stable_ releases will **not** be labeled, and follow semver from the last Beta release (e.g., "1.0.0")
+2. Update `docs/release-notes.md`:
+    - latest release is at the top, under a second-level header
+    - 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))
+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
+7. Edit the resulting GitHub Release
+    - Set the GitHub Release 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/[email protected]/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:  
 https://github.com/mozilla/testpilot/blob/master/docs/development/hosting.md
 
-This repository is in the "testpilot-mozillaextension" Jenkins pipeline.
+This repository is in the **"testpilot-mozillaextension"** Jenkins pipeline.
 The CloudOps team manages access to, and can help report on, the status of the
 builds.
+
+The resulting files deployed are:
+
+- Updates file for automatic browser extension updates: [https://testpilot.firefox.com/files/[email protected]/updates.json](https://testpilot.firefox.com/files/[email protected]/updates.json)
+- Latest version of the signed extension XPI: [https://testpilot.firefox.com/files/[email protected]/latest](https://testpilot.firefox.com/files/[email protected]/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.