See also the recent activity on the task tracker.

Be clearer on *who* can run the automated test suite on lizard.
Remove "also" that doesn't make sense anymore, since the previous paragraph was deleted.
updated PO files
Add articles in French and Portuguese
Group articles about 1.3
Improve the index of blueprints
Add press appearances
Revamp quite a bit the "running the test suite on lizard" doc.
Remove past dates
Remove the deprecated instructions for default user.name and user.email.
Reference the doc for developers to run the test suite on Lizard.
Add instructions for developers to run the test suite on Lizard.
Add TOC.
Blueprint: update the process to add a branch to the automated builds.
Integrate upgrade in the flowchart (Closes: #8838)
Doing a full upgrade from Tails also requires a temporary Tails.
Integrate upgrade in first screen
As a first approximation, upgrade is like installing but you're not a
first time user. So this replaces "first time user/yes" by
"installation" and "first time user/no" by "upgrade".
updated PO files
Add press appearance
Update design of tordate.
Clarify.
updated PO files
Agenda--
Remove solved problems
Move the web assistant blueprint under bootstrapping
Make design doc reflect the current state of things.
It is meant to change, but let's get ourselves a clean starting point :)
Clarify the locally-merge-before-building thingie.
Add bonus ideas.
Clarify wording and must/should/blah priorities.
Clarify notifications.
Mention GitLab's support of webhooks.
Move to GitLab for the "fork us on.." documentation.
Its UI is way nicer than repo.or.cz, it is easier to configure, it offers HTTPS,
and most importantly we can easily push there ourselves (to get an up-to-date
mirror, and e.g. remove old tags or rewrite history) as opposed to our old
mirror-style repo on repo.or.cz.
We don't create mirrors at repo.or.cz in practice anymore, and we don't need it anyway IMO.
Fix typo.
Rephrase a bit.
Ask *everyone* to first delete their local tags.
Otherwise, the old history will inevitably come back "thanks" to the 'jenkins-*'
and 'rm' buggy tags.
updated PO files
Move post-Git-rewrite doc in place.
Move one last branch around.
Polish doc.
It's now been tested.
updated PO files
Add known issue about NoScript 2.6.9.14 in Tails 1.3.
Fix date on release announcement.
releasing version 1.3
Clarify what kind of merges we're talking about.
Fix markup
Move Changelog down
Add usual structure
Reorder items
Tor Browser confinement will confuse many people, so raising priority.
Fix many technical concerns
This won't be needed in the end
Add another potential solution.
Point to the Changelog instead of Redmine
The status of tickets in Redmine is bound to change right after the
release.
Add anchor.
Rewrap
Remove parts that we have templates for
Document identified problem + {short,mid,long}-term envisioned solutions.
Remove trailing spaces
Importing release notes from last blueprint
Merge remote-tracking branch 'origin/master' into testing
Conflicts:
wiki/src/doc/advanced_topics/virtualization/virtualbox.fr.po
wiki/src/doc/anonymous_internet/Tor_Browser.de.po
wiki/src/doc/anonymous_internet/Tor_Browser.pt.po
wiki/src/news/test_1.3-rc1.fr.po
wiki/src/support/known_issues.fr.po
Clarify.
Fix typo.
Reformat.
Remove blueprint for 1.3 release notes, moving it to testing
Blueprint: add some more build stats.
Blueprint: add a clarification about feature branches being merged in base branch before builds.
Sanity check the Tor Browser version earlier.
updated PO files
Merge remote-tracking branch 'origin/doc/7226-torbrowser_new_identity'
Closes: #7470, #7709, #7226
Updating trace file after uploading 1.3.
Add alpha channel incremental upgrade path from 1.3~rc1 to 1.3.
This will ease testing of the 1.3~rc1_to_1.3 IUK.
Add alpha channel incremental upgrade path from 1.2.3 to 1.3.
This will ease testing of the 1.2.3_to_1.3 IUK.
Update upgrade-description files.
removed all remaining questions since those have been resolved
Update website PO files.
Update version and date for 1.3.
Mention electrum on the features page.
Merge remote-tracking branch 'origin/master' into testing
Conflicts:
wiki/src/contribute/how/donate.de.po
wiki/src/doc/about/fingerprint.fr.po
wiki/src/doc/about/openpgp_keys.fr.po
wiki/src/doc/about/warning.de.po
wiki/src/doc/about/warning.fr.po
wiki/src/doc/advanced_topics/cold_boot_attacks.fr.po
wiki/src/doc/anonymous_internet/unsafe_browser.fr.po
wiki/src/doc/anonymous_internet/vidalia.fr.po
wiki/src/doc/encryption_and_privacy/manage_passwords.fr.po
wiki/src/doc/encryption_and_privacy/truecrypt.fr.po
wiki/src/doc/first_steps/accessibility.fr.po
wiki/src/doc/first_steps/persistence/copy.fr.po
wiki/src/doc/first_steps/startup_options.fr.po
wiki/src/doc/first_steps/startup_options/bridge_mode.de.po
wiki/src/doc/sensitive_documents/graphics.fr.po
wiki/src/download.fr.po
wiki/src/inc/stable_i386_date.fr.po
wiki/src/news.de.po
wiki/src/news/who_are_you_helping.fr.po
wiki/src/press.fr.po
wiki/src/support/talk.fr.po
[fr] Tiny updates
Move branches around.
We won't have to manually rebase anything, apparently :)
Sort some more branches.
updated PO files
Make it clear this has been tested on Jessie only (Closes: #8929)
It's an advanced topic, so having tested instructions for other version
of Debian and Ubuntu is not a blocker, I think.