[gmx-developers] some notes on using redmine

Szilárd Páll szilard.pall at cbr.su.se
Sat Jan 8 21:13:13 CET 2011

Having a link from a bugfix commit to the report in redmine is in my
opinion important. Also very important is to actually file a proper
bug report if a bug affects _any_ released version and/or if it's
major/takes long time to fix. I suggest adding these to the
development guidelines.

Slightly unrelated, but in my opinion also important is the fact that
a bug/feature/task does not need to be assigned to someone at the time
of filing and when it gets assigned it means that somebody took the
responsibly to work on it.


On Sat, Jan 8, 2011 at 8:36 PM, Teemu Murtola <teemu.murtola at cbr.su.se> wrote:
> On Fri, Jan 7, 2011 at 01:56, Mark Abraham <Mark.Abraham at anu.edu.au> wrote:
>> I think it would be overkill to require the creation or linking of a Redmine
>> issue for every commit, however. Thoughts?
> Requiring it could indeed be overkill, but we could try to make it a
> strong recommendation.  This way, Redmine would get much more easily
> integrated into the workflow, because people would be forced to think
> about the issue at least a bit.  Adding something like IssueID #NNN at
> the end of a commit message should be enough (or perhaps configuring
> Redmine such that it would link commits that start with [#NNN]) in
> cases where the issue number does not naturally fit into the commit
> message.
> Another thing that would be worth thinking about is the formatting of
> the commit messages.  Many git tools, and it seems that Redmine as
> well, work somewhat better if commit messages are formatted according
> to the guidelines put forth in many git tutorials: first a max
> ~50-char line with a short summary, then an empty line, and then a
> more detailed description of the commit (many places suggest max 72
> character lines, and, e.g., gitk works badly with long lines).  If
> nothing else, this would make the activity page in Redmine more
> readable.
> Teemu
> --
> gmx-developers mailing list
> gmx-developers at gromacs.org
> http://lists.gromacs.org/mailman/listinfo/gmx-developers
> Please don't post (un)subscribe requests to the list. Use the
> www interface or send it to gmx-developers-request at gromacs.org.

More information about the gromacs.org_gmx-developers mailing list