Commit 0690b411 authored by sajolida's avatar sajolida
Browse files

More tricks on writing monthly reports

parent 067b218a
......@@ -14,11 +14,10 @@ Checklist
- <https://mailman.boum.org/pipermail/tails-ux/>
- <https://mailman.boum.org/pipermail/tails-project/>
- Explore the Git history:
- `git log --since="January 1" --until="February 1"`
- `git log --patch --since="January 1" --until="February 1"`
- XXX: Find a command to output the diff instead of the log here.
- Redmine view of closed issues:
- <https://labs.riseup.net/code/projects/tails/issues?utf8=%E2%9C%93&set_filter=1&f[]=closed_on&op[closed_on]=%3E%3C&v[closed_on][]=2016-01-01&v[closed_on][]=2016-01-31&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=author&c[]=assigned_to&c[]=updated_on&c[]=cf_9&group_by=>
- Redmine view of updated tickets that are still open or resolved:
- <https://labs.riseup.net/code/projects/tails/issues?utf8=%E2%9C%93&set_filter=1&f[]=updated_on&op[updated_on]=%3E%3C&v[updated_on][]=2016-01-01&v[updated_on][]=2016-01-31&f[]=status_id&op[status_id]=%3D&v[status_id][]=9&v[status_id][]=7&v[status_id][]=11&v[status_id][]=3&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=author&c[]=assigned_to&c[]=updated_on&c[]=cf_9&group_by=status>
- <https://labs.riseup.net/code/projects/tails/issues?query_id=212>
Publishing
==========
......@@ -42,13 +41,17 @@ Template
Releases
========
* [[Tails VERSION was released on MONTH DAY, YEAR|news/version_VERSION]] ([major|minor] release).
* [[Tails VERSION was released on MONTH DAY|news/version_VERSION]] ([major|minor] release).
* The next release (VERSION) is [[scheduled for MONTH DAY|contribute/calendar]].
* Tails VERSION+1 is [[scheduled for MONTH DAY|contribute/calendar]].
The following changes were introduced in Tails VERSION:
XXX: Copy release notes, and compact a bit if needed.
XXX: Copy the "Changes" section of the release notes, and compact a bit:
- Remove lines about software upgrade (that's not Tails itself).
- Remove screenshots.
- Remove "New features" and "Upgrades and changes" headlines.
- Remove line about Changelog.
Code
====
......@@ -70,22 +73,20 @@ XXX: Count the number of tests in /features at the beginning of next month
git checkout `git rev-list -n 1 --before="June 1" origin/devel`
git grep --extended-regexp '^\s*Scenario:' -- features/*.feature | wc -l
XXX: Add the diff from the previous month, for example:
XXX: Report only if more scenarios have been written and add the diff from the previous month, for example:
- Our test suite covers SCENARIOS scenarios, DIFF more that in May.
* In February XXX ISO images were automatically built and tested by our continuous integration infrastructure. XXX=ask tails-sysadmins@boum.org
* XXX ISO images were automatically built and tested by our continuous integration infrastructure. XXX=ask tails-sysadmins@boum.org
Funding
=======
XXX: Look at the fundraising Git.
XXX: The fundraising team should look at the fundraising Git.
gitk --all --since='1 December' --until='1 January' origin/master
git log --patch --since='1 December' --until='1 January' origin/master
XXX: Look at the <tails-fundraising@boum.org> and <tails-accounting@boum.org> archives.
ask -> tails-fundraising@boum.org
XXX: The fundraising and accounting teams should look at the archives of <tails-fundraising@boum.org> and <tails-accounting@boum.org>.
Outreach
========
......@@ -104,6 +105,8 @@ XXX: Link to the thread on <https://mailman.boum.org/pipermail/tails-XXX/>.
Press and testimonials
======================
XXX: Copy content from press/media_appearances_2016.mdwn
Translation
===========
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment