PMML Issue Management Process

 

The procedure below defines the steps that the Data Mining Group follows to manage changes  to the standard. 

 

1. An individual (the “Finder”) identifies an defect or enhancement for PMML
2. The finder opens a new issue in the SourceForge PMML Project (http://sourceforge.net/projects/pmml) via the Tracker application which is accessed using the Develop selector (https://sourceforge.net/tracker/?group_id=56177).
1. The finder selects the Tracker that appropriate for the issue: 

·   V4.0 Bugs:  Used to track issues with the currently released version of the standard (see Note)

·   V4.1 Feature Requests:   Used to track issues targeted for the next release of the standard (see Note)

·   Feature Requests, Patches, Support Request:  Used only by non-project members, issues opened in these trackers will need to be moved to the appropriate V4.0 or V4.1 Tracker.

Note: The finder must be member of the SourceForge PMML Project to see these current Trackers.  To join the project, send a message to Ashok_S via the PMML Member List (https://sourceforge.net/project/memberlist.php?group_id=56177)

2. Use the Tracker’s “Add New” button and enter the following information:

                                          i.    Category:  Specify the relevant PMML section (which map to the HTML documents that comprise the standard)

                                         ii.    Private:  Not used

                                        iii.    Group:  Not used

                                       iv.    Assigned:  Based on the category, that section’s owner will be auto-assigned; or, another owner can be specified.  It’s common for the finder of an issue to also be the one to make the proposal for resolving the issue and, in these cases, the Finder should be assigned the issue.

                                        v.    Priority:  Relative importance to the Finder for getting this issue resolved

                                       vi.    Summary:  Brief description of the defect/enhancement

                                      vii.    Details:  Detailed explanation of the defect/enhancement

                                     viii.    Attachment:  If possible, attach proposed solution (see step 3)

3. Solution to the issue is proposed:  This is done by marking up a copy of the relevant HTML document:
1. Download the currently released version of the relevant HTML document(s):

                                          i.    From the SourceForge PMML Project page, using the Develop selector and then the Code selector to run the CVS Browse utility (http://pmml.cvs.sourceforge.net/pmml/)

                                         ii.    From the list of folders, select the “htm-Vx-y-z/” folder for the latest released version of PMML, where x-y-z is the release number (e.g., for PMML 4.0, select “htm-V4-0-0/”)

                                        iii.    From the list of files, download the latest version of the document(s) will need to modify to create your proposal.

2. Modify the document according to these guidelines:

                                          i.    Rename the files to reflect the nature of proposal/modifications (e.g., to fix typos in the Time Series specification, change “TimeSeriesModel.html” to “TimeSeriesModel_FixTypos.html”)

                                         ii.    Use a plain text editor to make changes to the file.  All html editors remove certain tags that we need to create the XSD, not to mention reformatting, etc.

                                        iii.    Wrap changes/additions in <new> and <font color=red> tags.  Example:  <new><font color=”red”>This is a new feature.</font></new>

                                       iv.    Wrap deletions with <s> (for strikethrough).  Example:  <s>This text is deleted.</s>

3. eMail the proposal and its marked up document to the PMML mailing list (pmml-standard@lists.sourceforge.net).
4. If not already done in Step 2, attach proposal to issue.
5. Change the issue’s Response field to “In Review”
4. DMG acts on the proposal:  Once the DMG members have had a chance to review the proposal and discuss, the DMG will either:
1. Approve the proposal:  Change the issue’s Response Field to “Approved” and the Resolution Field to “Accepted”.
2. Reject the proposal:  Change the issue’s Response Field to “Rejected” and the Resolution Field to “Rejected”.
3. Revise the proposal:  The proposed solution is revised based on feedback from the DMG.  Change the issue’s Response Field to “In Revision”.
5. Approved proposals are merged into Source Control
1. The DMG Source Control Manager (currently Ashok) will merge the solution into CVS.  Change the Status field to “Closed”.