Feature #9331

Write release notes for 1.4

Added by sajolida 2015-05-03 09:47:56 . Updated 2015-05-11 15:02:48 .

Status:
Resolved
Priority:
Elevated
Assignee:
sajolida
Category:
Target version:
Start date:
2015-05-03
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Last time for 1.3 we did something funky with the release notes open to edition in a blueprint. This was quite complicated to handle between testing and master, links to pieces of documentation that were not existing yet, Git hard to analyse, etc. I didn’t like it so much.

This time I propose that we use the same Git setup as before 1.3 but that we try to work on the draft a bit more collectively.

We should base our work on the release notes for the RC.


Subtasks


History

#1 Updated by sajolida 2015-05-03 09:48:33

  • Status changed from New to Confirmed
  • Assignee set to anonym

anonym, please reassign this to me once you’re done with a first dump of information.

#2 Updated by sajolida 2015-05-03 09:57:40

  • Description updated

#3 Updated by sajolida 2015-05-03 10:04:21

  • Description updated
  • Assignee changed from anonym to sajolida
  • Priority changed from Normal to Elevated

#4 Updated by sajolida 2015-05-06 15:47:08

  • Status changed from Confirmed to In Progress

Applied in changeset commit:579abd8f5adc8c2394529f81a3328cdffea2b101.

#5 Updated by sajolida 2015-05-06 15:47:45

  • Assignee deleted (sajolida)
  • QA Check set to Ready for QA

#6 Updated by BitingBird 2015-05-06 18:10:45

  • Maybe the release notes could link to the new doc, for example a link to TB security slider would be nice.
  • The 3 first items should mention Tor Browser instead of just Tor, from the description it applies only to the browser.
  • “command line client” -> “command-line clients”
  • “the default Firefox tab is user” ??

#7 Updated by BitingBird 2015-05-06 18:11:00

  • Assignee set to sajolida
  • QA Check changed from Ready for QA to Dev Needed

#8 Updated by sajolida 2015-05-07 15:18:26

  • Status changed from In Progress to Resolved
  • QA Check changed from Dev Needed to Pass
  • Added a link to the security slider doc.
  • GDSG says “command line” without hyphen and so do we in the rest of the doc.
  • The rest has been solved already.

#9 Updated by sajolida 2015-05-07 17:14:56

  • Status changed from Resolved to In Progress
  • QA Check changed from Pass to Dev Needed

I still need to point to the Claws Mail advisory.

#10 Updated by sajolida 2015-05-11 12:11:43

  • Status changed from In Progress to Resolved
  • QA Check deleted (Dev Needed)

Done in 1f36179.

#11 Updated by intrigeri 2015-05-11 12:54:51

  • Status changed from Resolved to In Progress

The last commits let users believe that we had stream isolation in the browser pre-1.4, which is untrue.

#12 Updated by sajolida 2015-05-11 14:51:50

  • Status changed from In Progress to Resolved

Fixed in commit:cd21424.

#13 Updated by BitingBird 2015-05-11 15:02:48

  • QA Check set to Pass