Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-25 Thread Michael Glavassevich
- > us...@xerces.apache.org > Date: 04/23/2018 08:08 AM > Subject: Re: [REVISED VOTE]: Xerces-J 2.12.0 release > > Hi all, >The 1st voting for Xerces-J 2.12.0 release was stopped, due to > certain issues that were in the release candidates (RC) that were > found by the reviewers ([

Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-24 Thread Gareth Reakes
+1 Thanks for the work everyone! Gareth > On Apr 23, 2018, at 1:06 PM, Mukul Gandhi wrote: > > Hi all, >The 1st voting for Xerces-J 2.12.0 release was stopped, due to certain > issues that were in the release candidates (RC) that were found by the > reviewers ([5]). Those have been fi

RE: [EXTERNAL] Re: [VOTE]: Xerces-J 2.12.0 Release

2018-04-23 Thread David Dillard
Gandhi [mailto:muk...@apache.org] Sent: Saturday, April 21, 2018 1:05 AM To: j-...@xerces.apache.org Cc: priv...@xerces.apache.org; j-users@xerces.apache.org Subject: [EXTERNAL] Re: [VOTE]: Xerces-J 2.12.0 Release Hi Michael & all, I've fixed all the below mentioned issues that were

Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-23 Thread Mukul Gandhi
Hi all, The 1st voting for Xerces-J 2.12.0 release was stopped, due to certain issues that were in the release candidates (RC) that were found by the reviewers ([5]). Those have been fixed now, and I'm initiating this new mail for the Vote for new RC. I've uploaded Xerces-J 2.12.0 release candi

Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-23 Thread Mukul Gandhi
On Mon, Apr 23, 2018 at 4:51 PM, sebb wrote: > > I alone can't decide on this (though I sort of agree with you). Lets see > how > > others react to the topic of having or not having MD5 hashes, and we can > > accordingly finalize as this voting concludes. > > The ASF policy was updated recently,

Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-23 Thread sebb
On 23 April 2018 at 11:04, Mukul Gandhi wrote: > On Sun, Apr 22, 2018 at 3:19 PM, sebb wrote: > >> Contains MD5 hashes; these are deprecated and should be removed. > > > I alone can't decide on this (though I sort of agree with you). Lets see how > others react to the topic of having or not havin

Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-23 Thread Mukul Gandhi
On Sun, Apr 22, 2018 at 3:19 PM, sebb wrote: Contains MD5 hashes; these are deprecated and should be removed. > I alone can't decide on this (though I sort of agree with you). Lets see how others react to the topic of having or not having MD5 hashes, and we can accordingly finalize as this votin

Re: [REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-22 Thread sebb
On 21 April 2018 at 06:27, Mukul Gandhi wrote: > Hi all, >The 1st voting for Xerces-J 2.12.0 release was stopped, due to certain > issues that were in the release candidates (RC) that were found by the > reviewers ([5]). Those have been fixed now, and I'm initiating this new mail > for the Vot

[REVISED VOTE]: Xerces-J 2.12.0 release

2018-04-20 Thread Mukul Gandhi
Hi all, The 1st voting for Xerces-J 2.12.0 release was stopped, due to certain issues that were in the release candidates (RC) that were found by the reviewers ([5]). Those have been fixed now, and I'm initiating this new mail for the Vote for new RC. I've uploaded Xerces-J 2.12.0 release candi

Re: [VOTE]: Xerces-J 2.12.0 Release

2018-04-20 Thread Mukul Gandhi
Hi Michael & all, I've fixed all the below mentioned issues that were found in previous RC, within the revised RC for 2.12.0 release. I'll shortly be writing a separate mail, for the Vote for new RC. On Fri, Apr 20, 2018 at 2:29 AM, Michael Glavassevich wrote: > Should fix the copyright years

[VOTE]: Xerces-J 2.12.0 Release

2018-04-19 Thread Mukul Gandhi
Hi all, I've uploaded Xerces-J 2.12.0 release candidates to [1] for review. In this release candidate there are two sets of packages, the main release built from the trunk [2] and the XML Schema 1.1 release built from the XML Schema 1.1 development branch [3]. The change summary is available he