Re: Any Xerces-J 2.12.0 release date to address CVE-2012-0881?

2018-01-11 Thread Michael Glavassevich
A lot of what needs to get done requires write-access and that can only be done by committers [1]. That's where this project has been hurting for a long time and where we definitely need help. Of course there are activities such as testing or doing a build that anyone could do, but someone with

Re: Any Xerces-J 2.12.0 release date to address CVE-2012-0881?

2018-01-11 Thread Eric J. Schwarzenbach
One might expect "commiter" to imply a coder, but could someone who is not going to actually work on xerces code be made a committer? If so, what skills would such a person need in order to help get the release out? On 01/11/2018 01:42 PM, Michael Glavassevich wrote: A lot of what needs to get

Re: Any Xerces-J 2.12.0 release date to address CVE-2012-0881?

2018-01-11 Thread Michael Glavassevich
Some of these steps are out-of-date but this [1] should give you a general idea of what's involved in preparing a release. I think some projects have had committers who just wrote documentation or contributed in other non-coding ways so that's certainly a possibility. Thanks. [1] http://xerces