Personally, I am panicking. I've been promoting jBPM to my customer as the best thing out there. They were relucant to go with an open source solution, but I assured them that RedHat support was available. (I asked for a quote for support specifically for jBPM 4.x, was told I need SOA-P. I got a quote for SOA-P, but only just realized it does not include jBPM4). Now I have to go back to my customer and tell them support will not be available. And moreover, there will be major changes moving to a future release.
I understand the need/desire to merge jBPM and Drools Flow in a future version. I don't have an issue with that. What I am concerned about is the lack of a statement of commitment by RedHat *management* (no offense Alejandro) to complete the planned features for jBPM 4, create a production quality release and provide support until a production-ready jBPM5 is available.