4 Replies Latest reply on Jul 3, 2008 2:30 AM by Thomas Diesler

    jBPM3 should release lock-step with jPDL4

    Thomas Diesler Master

      Folks,

      looking at the road map, I see

      jBPM jPDL 3.2.4 (01-Sep-2008)
      jPDL 4.0 alpha1 (01-Aug-2008)
      jPDL 4.0 alpha2 (11-Sep-2008)

      First, I think we should have a consistent naming scheme (i.e. either we use the jBPM prefix or not)

      Second, it is important that the releases go lock-step with respect to the API. Only if the functionality offered through the API has an actual implementation in both code bases we can be sure that it is the API that we want.

      For details of the process see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138168

      Therefore I propose for jPDL4 a release cycle that aligns with jBPM3. Faster than eight weeks is very hard to manage anyway given the documentation and test coverage that is required.