• issue resolution process

To report issues about the specification, just send an email to issues@omg.org mentioning BPMN 2.0. If you prefer an online form, go to this link to accept the agreement and then move on to submit the issue.

After the OMG posts a submitted issue we will import that issue into JIRA. We will use JIRA to track the status and internal discussions about the issues, but we will not use JIRA to generate new issues.

Given the way the issues are created, via email from Juergen, the summary and description of the issue in JIRA is not proper. This is why the first person editing the issue must also perform some administrative editing:

• Change the summary of the issue to something more meaningful (change from “OMG Issue Created XXXX” to ”[OMG XXXXX] Typo mistake in section X.Y.Z”)
• Remove all the signature and other undesired text (created from, etc.)
• add a line at the top of the description with the person reporting the issues in this format: ##Source: Company (Name, email)

Now, after this is done, issue coordination team must change the following field:

• The Component, which will define the sub-group in charge of the issue
• The assignee, which will “own” resolution of the issue

Once there is proposed resolution (could be no-action, resolved, etc), this resolution is informed in JIRA by appending a line to the description with the following format:

• ##Proposed Resolution: Resolved

Should more than one resolutions are propose, you just add 2 lines with the same pattern

We will vote for the resolutions to multiple issues (e.g., 10) with each poll.

The polls for voting on the issues can be found here.

• Poll 1 is here and completed on 2009-10-27 (results here and here)
• Poll 2 is here and completed on 2009-11-17 (results here and here)
• Poll 3 is here and completed on 2009-12-08 (results here and here)
• Poll 4 is here and completed on 2009-12-24 (results here and here)
• Poll 5 is here and completed on 2010-01-28 (results here and here)
• Poll 6 is here and completed on 2010-02-16 (results here and here)
• Poll 7 is here and completed on 2010-03-03 (results here and here)
• Poll 8 is here and completed on 2010-03-23 (results here and here)
• Poll 9 is here and completed on 2010-04-06 (results here and here)
• Poll 10 is here and completed on 2010-04-22 (results here and here)
• Poll 11 is here and Completed on 2010-05-05
• Poll 12 is here and Completed on 2010-05-06
• Poll 13 is here and Completed on 2010-05-21

The following timeline have been adopted

• March 9: Ballot #8
• March 22: Decide on how to proceed with C-Merger (Note: For the C-Merger discussion: We need by March 18 complete MM, complete XSD schema (for C-Merger) and initial draft of the spec text for the review on March 22)
• March 23: Open Ballot #9 (resolutions for all unassigned issues also to be included)
• April 6: Open Ballot #10 (deadline for all critical issues)
• April 20: Open Ballot # 11 (deadline for all non-editorial issues ). Note: Announced resolutions - DI proposal to be included in this ballot
• April 23: Draft of the specification package (+CMOF) including passed resolutions (ballots 7-9).
• April 27: Open Ballot #12 (for remaining editorial issues). Note: There is one week for vote
• May 4: Ballot #13 (all issues to be deferred)
• May 4 – 9: Incorporate remaining resolutions and consolidate the document, XSD, XMI (ballots 10 and 12 included), CMOF
• May 10 – 16 Final review of the specification package
• May 17 – 19 Final editing
• May 20 – 21 Generate final report
• May 24: FTF Report available

The following action items have been agreed

• @All assignees: Consider the ballots schedule and provide your estimate (by March 22) when (in which ballot) you can provide issue resolutions. All unscheduled (not assigned to ballots) will be considered as unassigned and we will follow the same procedure as for other unassigned issues. For March 22: Please be conservative and if you have feeling please unassign the issues
• Issues not resolved by April 20 will be deferred

• Issue Coordination Sub-Group
• Editors Sub-Group
• Interaction Sub-Group
• SoaML Coordination Sub-Group
• Process Orchestration Sub-Group
• Diagram Interchange Sub-Group
• Examples Sub-Group

• Meeting Minutes
• Presentations, Examples
• Report

• BPMN 2.0 Specification dtc-2010-05-03 - No Markup
• BPMN 2.0 Specification dtc-2010-05-02 - Markup
• BPMN 2.0 Specification, Beta -- FTF Internal Draft 3 -- Ballots 1 - 12
• BPMN 2.0 metamodel and schema -- FTF Internal Draft 3 -- Ballots 1 - 12
• BPMN 2.0 Specification, Beta -- FTF Internal Draft 2 -- Ballots 1 - 10
• BPMN 2.0 XSD, Beta -- FTF Internal Draft 2
• BPMN 2.0 Metamodel (RSA/RSM), Beta -- FTF Internal Draft 2
• BPMN 2.0 CMOF, Beta -- FTF Internal Draft 2, Ballots 6-10 (not including c-merge)

• BPMN 2.0 Specification, Beta -- FTF Internal Draft 1
• BPMN 2.0 XSD, Beta -- FTF Internal Draft 1
• BPMN 2.0 Specification, Beta 1
• BPMN 2.0 Specification, Beta 1 - Word Document Files (for proposal generation)

• BPMN2FTF Issues on JIRA
• BPMN2FTF Issues on OMG site
• BPMN 2.0 FTF OMG Work in Progress Page
• BPMN 2.0 RFP OMG Work in Progress Page
• BPMN.org Web Site

administration