Folks,
starting with jbpm-3.2.3.GA we will have a release cycle of eight weeks per minor release. The motivation is to improve the predictability of the jbpm releases, therefore we will follow the following rules:
| ---------------------------------
| W1
| W2 Define set of JIRA issues (Jira Freeze)
| ----------------------------------
| W3
| W4
| W5
| W6 Work on issues (Code Freeze)
| ----------------------------------
| W7
| W8 QA, Docs, Packaging (Release)
| ----------------------------------
|
In other words, at the end of W2 there are no more JIRA issues added to a release. At the end of W6 there are no more code changes.
Please check out the road map for for upcoming releases.
http://jira.jboss.com/jira/browse/JBPM?report=com.atlassian.jira.plugin.s...
Cheers
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160921#4160921
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160921
Hi Koen,
what is the status of this?
http://jira.jboss.com/jira/browse/JBPM-1197
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
CVS is dead for HEAD. SOA branches should be created in SVN
-thomas
Tom Baeyens wrote:
> I see 3 SOA releases in JIRA:
>
> jBPM 3.2.2 SOA 1 : a lot of closed issues associated to it.
> SOA 4.2 CP03 : the next release of the platform
> SOA 4.3 : a future release (2009H2) of the platform
>
> I don't remember to which soa platform release "jBPM 3.2.2 SOA 1"
> corresponds. I'll mark this as 'released' since all issues are closed.
>
> Can all of you make sure that all bug fix that are applied to HEAD also
> get applied to the BRANCH_3_2_2_SOA_4_2 When you do this, make sure the
> fix version is also set to "SOA 4.2 CP03" to indicate that it's fixed in
> the SOA branch.
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx