I agree with Knut that this is a procedural issue which could be handled
by a lazy consensus vote: http://www.apache.org/foundation/voting.html .
Although we've been discussing the topic for a couple days, we haven't
done so under the aegis of a formal vote. Thanks to Myrna for offering
to call the lazy consensus vote and then file the INFRA issue afterward.
The vote will only add 72 hours of delay to the process.
Thanks,
-Rick
On 5/29/13 12:53 PM, Myrna van Lunteren wrote:
You could ask infra if it works after closure...
How shall we proceed, I can call a vote on it and if everyone's in
favor, I can log an INFRA issue...
Myrna
On Tue, May 28, 2013 at 9:15 PM, Dag Wanvik <[email protected]
<mailto:[email protected]>> wrote:
On 28.05.2013 22:58, Rick Hillegas wrote:
> +1. From the CLOUDSTACK example, it looks like the svngit2jira
trigger
> attaches the whole commit comment to the issue. That's useful
> information to see on the issue. It would save me the manual step of
> mousing my commit stamps into comments.
>
Does the scheme work if the issue has been closed (erroneously,
presumably..)? For manually added comments the issue needs to be open.
Could perhaps be an issue for after-close type fixes etc..
Thanks,
Dag
