----- Original Message -----
From: "Gabe Alford" <redhatrises(a)gmail.com>
To: "SCAP Security Guide" <scap-security-guide(a)lists.fedorahosted.org>
Sent: Wednesday, September 3, 2014 4:02:04 PM
Subject: Re: Implementing GitHub Milestones
Speaking about blockers (issues that definitely need to go into next release)
would it be possible to set up an agreement that such fixes would receive the
[BLOCKER] prefix together with the [PATCH] prefix?
Are you talking about adding a "Blocker" label to the pull request? Or when
you `git commit` adding "[Blocker]" to your commit msg before you initiate a
Basically both of them might be handy. "Blocker" label in the pull request due
to the fact, often the pull request contains more than just one patch (not to
need repeatedly insert them for bigger patchset).
For case of committing - corresponding git hook (checking if the git log message
contains at least one of [blocker], [bugfix], [enhancement], .. any others?)
would be handy to prevent log messages not specifying type of change.
Thank you && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Technologies Team