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?).
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. It takes more time on your end, but it assures the developer he isn't spending time in invalid bugs and it makes it really easy for him to see the code quickly on the github. 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 accurate. 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" > when > f1 : MyEvent( key == "faultType1", value == "ALARM" ) over > window:length( 1 ) > f2 : MyEvent( key == "faultType2", value == "ALARM" ) over > window:length( 1 ) > then > System.out.println( "************ both faults are active! f1.key = > " + f1.getKey() + " f2.key = " + f2.getKey() ); > end > > 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. > > -W > _______________________________________________ > rules-dev mailing list > rules-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev > -- With kind regards, Geoffrey De Smet _______________________________________________ rules-dev mailing list rules-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev
