7 Replies Latest reply on May 25, 2010 12:51 PM by swiderski.maciej

    jBPM 4.4 announcement

    aguizar

      We are down to 9 unresolved issues left before releasing 4.4. Of these, two are assigned to Maciej and five to me. Huisheng has already resolved all issues he took for himself - much appreciated! Given the current progress, it should be possible to release jBPM 4.4 on June 4th; the date is of course tentative and subject to change.

       

      If you feel like there is an issue that cannot be left out, the time to bring it up is now. Right now the only blocker issue is JBPM-2872: fix hudson db job. All others are deferrable if not completed on time.

        • 1. Re: jBPM 4.4 announcement
          swiderski.maciej

          HI Alejandro,

           

          Great to hear that there is a date for 4.4 release. I think it is highly awaited by the community.

           

          If it comes to issues assigned to me I would say I am pretty much done with them is just to get your opinion before check in.

           

          In addition, I suggest to include (if you will agree with solution) for each for fork activity. Mainly as developer ready release to get feedback on it.

           

          Looking forward to your opinion.

           

          Thanks

          • 2. Re: jBPM 4.4 announcement
            rebody

            Hi Alejandro,

             

            It is a really good news for us.  Finally we could get jBPM 4.4 to release.  And there are still two weeks before the releasing date.  I think it is enough for us to handle the rest of issues

            • 3. Re: jBPM 4.4 announcement
              swiderski.maciej

              Hi,

               

              I just want to inform you that I marked two issues to be included in 4.4 release that are ready to be checked in:

              - fork with for each support (https://jira.jboss.org/browse/JBPM-2414)

              - fix for incorrect behavior of join activity with multiplicity attribute (https://jira.jboss.org/browse/JBPM-2720)

               

              Hope we can include it, both of them are quite important in my opinion.

               

              Cheers,

              Maciej

              • 4. Re: jBPM 4.4 announcement
                aguizar

                Maciej, JBPM-2720 is an easy decision, please commit if you haven't already. As for JBPM-2414, I'd like to take a closer look at it to iron out any wrinkles, we also need to consider the documentation additions. Thank you for your great job so far.

                • 5. Re: jBPM 4.4 announcement
                  swiderski.maciej

                  ok, will commit JBPM-2720 today including test cases.

                   

                  I will prepare new patch for JBPM-2414 and attach it to jira for your review. While waiting for your review will work on some documentation and examples.

                  • 6. Re: jBPM 4.4 announcement
                    swiderski.maciej

                    BTW, I think we could include as well latest version of BPM console in 4.4 release as well. There are few interesting features available:

                    - process instance history

                    - possibility to signal process instance

                    - some bug fixes

                     

                    As far as I remember 2.1 version of BPM console was planned to be released and of April.

                    • 7. Re: jBPM 4.4 announcement
                      swiderski.maciej

                      2720 is not checked in.

                       

                      I attached new patch for 2414 to jira so please have a look at it.

                       

                      Another two issues are waiting for a review:

                      variable declaration with history support: https://jira.jboss.org/browse/JBPM-2506

                      documentation and examples for variable declaration https://jira.jboss.org/browse/JBPM-2776

                       

                      I got some feedback from HuiSheng (rather positive) and I think I am quite done with them as well.