On 22/06/2012, Geoffrey De Smet <ge0ffrey.spam(a)gmail.com> wrote:
If you're sure it's a bug, it's probably a good idea to
raise a jira too
(and link it in any mail correspondence about it).
That way it has a status (is it still open or is it already resolved for
the next release?).
The number of my JIRAs that remain open is considerable.
But to really get the ball rolling sooner rather then later for an
issue: create a pull request with an isolated regression test, for
example on MiscTest.
I invest enough work to identify the bug, and isolate it in a small
stand-alone application that can be run from the command line.
Currently I just don't have the resources to run git to stay
up-to-date and create pull requests. My small apps can be run just as
easily and more swiftly as a test in some framework.
If there were an easy way to upload such a stand-alone app, I'd do it.
It takes more time on your end, but it assures the developer he
spending time in invalid bugs
I'm not saying that I never raised an invalid bug, but that has
happened very, very rarely. And I consider pointing out an issue on
the mailing list as an invitation to comment or review, just to get a
"second opinion". But if this is ignored, then I don't bother any
and it makes it really easy for him to see the code quickly on the
Just take a look on the track record of pull requests for bugs (not
features), they are handled swiftly.
Note: I am not saying we shouldn't pick up on bugs reported on the
mailing lists (we try to),
but pull requests naturally get priority because they are far more
Op 22-06-12 20:36, Wolfgang Laun schreef:
> Lately, I have occasionally tried to raise an alert for something I
> consider a bug, but there was no comment.
> Here's another one.
> rule "Faults coincide"
> f1 : MyEvent( key == "faultType1", value == "ALARM" ) over
> window:length( 1 )
> f2 : MyEvent( key == "faultType2", value == "ALARM" ) over
> window:length( 1 )
> System.out.println( "************ both faults are active! f1.key =
> " + f1.getKey() + " f2.key = " + f2.getKey() );
> This rule fires after the insertion of a single fact matching the
> event bound to f1.
> Detailed code can be found on the user's list.
> rules-dev mailing list
With kind regards,
Geoffrey De Smet
rules-dev mailing list