Next Steps for 2.12.0 release

[David Costanzo <da...@yahoo.com.INVALID>]

On the xerces-j-users email list, Michael Glavassevich suggests that if there were volunteers to drive it, then Xerces version 2.12.0 could be released.  He suggested that volunteers do three things: 1) update the release notes in JIRA, 2) update the Xerces documentation, and 3) help with testing.


I have finished Step 1, which was to compile the release notes[1].  My method was to use a query[2] and tag all Fixed/Implemented/Done/Auto Closed/Pending/Closed tickets whose subversion change was made in trunk.  I stopped once I got to tickets that were opened prior to the 2.11.0 release.  This method is based on my understanding that changes in the xml-schema-1.1-dev branch will NOT be included in the release, so I did not include them (I kept a list of these, however).  It also excludes duplicate/invalid/etc. from the release notes, which I think is correct.  One flaw in this method is that if a fix is for a bug that was introduced after 2.11.0, but never released, it's still included in the release notes.  To me, this feels wrong, but I don't know how to correct for this.


While I was sorting through JIRA, a colleague of mine has created XERCESJ-1670 to port a fix from 
xml-schema-1.1-dev to trunk.  Unless this fix can be accepted in trunk, the 2.12.0 release won't be useful to my organization and I won't be granted time to continue assisting with the release.

As for what tasks remain before we can release 2.12.0, there's updating the Xerces documentation, which I believe is just the human-readable release notes at [3].  So I presume the expected update method is to open a JIRA ticket with a patch.  Is this correct?

As for the "help with testing" task, I need more clarity on what should be done and how it should be tracked.  I have noticed that "ant test" in trunk shows failures, despite printing "BUILD SUCCESSFUL" at the end (for example, I see 7 failures under "Running schema.config.AllTests").  Is this expected?  Do these need to be investigated and fixed before 2.12.0 can be released?  (I tried to reproduce this in the Xerces-J_2_11_0 tag but couldn't build the tag due to missing methods in HTMLFrameElementImpl.java).



[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10520&version=12336542
[2]

https://issues.apache.org/jira/issues/?jql=project%20%3D%20XERCESJ%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20resolution%20in%20%28Fixed%2C%20Implemented%2C%20Done%2C%20%22Auto%20Closed%22%2C%20%22Pending%20Closed%22%2C%20Resolved%29%20AND%20fixVersion%20%3D%20EMPTY
[3] https://svn.apache.org/repos/asf/xerces/site/trunk/production/xerces2-j/index.html

---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org