From: Michael Glavassevich <mrgla...@ca.ibm.com> > The release notes in JIRA (e.g. 2.11.0 notes [1]) and updates to the > Xerces documentation [2] are something anyone could help us out with. We
> likely have a bunch of broken links that should be fixed up. I started with the JIRA release notes [1] and it doesn't look like I have permissions to help with this. It looks to be generated automatically from the "Fix Version" of tickets, which I don't have permission to change. I think I can grovel through JIRA to identify which fixes will be included in 2.12.0. From what I can tell, the candidates are everything in JIRA that is "Fixed" with no "Fix Version" set[2] (which has 1168 tickets). Then some manual verification is needed for each ticket to confirm that comment indicates a subversion revision whose changes was made in "trunk" and whose revision is after r1039547 (when the branch for 2.11.0 was made). Does this sound correct? As mentioned previously, the fix that my organization wants (XERCESJ-1591, r1396551) was made in the "xml-schema-1.1-dev" branch, not trunk, so that branch would have to be merged back to trunk (or the fix duplicated in trunk) in order for a 2.12.0 release to benefit my organization. [1] https://issues.apache.org/jira/browse/XERCESJ/fixforversion/12336542 [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20XERCESJ%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%20EMPTY --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
