Hi David, David Costanzo <david_costa...@yahoo.com> wrote on 06/15/2016 10:11:18 AM:
> From: David Costanzo <david_costa...@yahoo.com> > To: "j-users@xerces.apache.org" <j-users@xerces.apache.org>, > Date: 06/15/2016 10:12 AM > Subject: Re: Interaction between redefine+include breaks augmenting > a base schema's element with new attributes > > 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 just add you to the list of contributors in JIRA. Hopefully that also granted you permission to update that field. > 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? XML Schema 1.1 specific fixes and improvements will only be on the "xml-schema-1.1-dev" branch. If we missed something more generic (i.e. also applies to XML Schema 1.0) then we should get that merged back on to the trunk. I think in general, any JIRA resolved with a fix after November 30th, 2010 (release date of Xerces-J 2.11.0) should be marked as being fixed in 2.12.0. > 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. I'll take a look at the original fix. Assuming it applies to XML Schema 1.0, it should have been committed at the same time to the trunk. > [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 Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
