2009/6/16 Tom Baeyens
<tbaeyens@redhat.com>
for making the release, there is only the effort of releasing. that is not a lot of effort so we can do it once and a while. so rest assured. it's not a political decision.
jbpm 3 already went through a lot of stabilization. so there is also the risk that if we fix something, that we introduce another problem.
So it is not only the effort of releasing, but also some additional QA (Stabilization != full QA, I know) ? Otherwise you would not be so reluctant (besides putting in the effort to fix the issue itself)
but for fixing the bugs, we are not proactively fixing all the bugs that people report on jbpm 3. we currently intend to only fix those that come from clients. and even for those reports we evaluate if the risk of introducing new problems when fixing the given bug.
But this is a different statement compared to 'there are no more jBPM3 releases planned'). Would make a lot of sense to make this fully clear in the community. Effectively jBPM 3 goes into a maintenance mode where paying customers drive the possibility of next releases'. But does this mean I should not put in any fixes anymore (not that I did that a lot, but others did) just to prevent possible regressions? Or should I only put them in trunk? Or? Please guide us ;-)
i think we need to spend most bugfixing efforts on jbpm 4.
I do not disagree with this, but I also agree with Bernd, jBPM 3 has a broad installed base. For me, jBPM 3 should at least have one more year of more development than what you suggest.
--
regards, tom.
Bernd Rücker wrote:
Tom Baeyens <https://jira.jboss.org/jira/secure/ViewProfile.jspa?name=tom.baeyens%40jboss.com> - 15/Jun/09 03:45 AM
there are no more releases planned for jbpm 3
Is this true? Only SP releases for bugfixes? But isn't this a 'bug'? The schema allows it.
------------------------------------------------------------------------
_______________________________________________
jbpm-dev mailing listhttps://lists.jboss.org/mailman/listinfo/jbpm-dev
_______________________________________________
jbpm-dev mailing listhttps://lists.jboss.org/mailman/listinfo/jbpm-dev