[Bf-committers] Automating setup of missing release notes page

Julian Eisel eiseljulian at gmail.com
Thu Oct 1 02:14:27 CEST 2015

Hey again,

As written in my previous mail [1], I set up a list for missing
release notes again. For the first time I used a script for this,
namely an expanded version of our git_log_review_commits_advanced.py
script [2] (can push changes to upstream if wanted). We already use it
to setup the release notes bug fixes page.

However, currently there's still *a lot* of tedious manual work
needed, since the script basically filters out commits with typical
non-feature wordings in the commit title.
(In numbers, I had to manually review 590 results, reducing it to 130,
which I then had to individually check if they are listed in the
release notes pages :S)

Some months ago, Campbell and I brainstormed how we could automate
this a bit. At least the process of collecting the actual feature
commits (or the commits which should be added to release notes).
We came up with ideas like using tokens to categorize commits, but now
I think we could go with a bit more simple & stupid solution.
Idea: For bug fixes we usually start the commit title with "Fix TXXXX"
or similar. Maybe we could start feature commits with "Feature:",
"Fe:", etc? Of course we had to get used to this, but IMHO organizing
commits a bit better won't hurt.

Feedback/Ideas welcome,
- Julilan -


[1] http://lists.blender.org/pipermail/bf-committers/2015-October/045962.html
[2] https://git.blender.org/gitweb/gitweb.cgi/blender-dev-tools.git/blob/HEAD:/utils/git_log_review_commits_advanced.py

More information about the Bf-committers mailing list