Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Cantor, Scott
On 2/17/15, 3:01 PM, Boris Kolpackov bo...@codesynthesis.com wrote: See it from my POV: I have a ton of users that are pretty happy with 3.1.1. Now comes Scott and wants to cut a half-tested release just to satisfy his immediate needs. Once you do this I will start getting emails from my users

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Boris Kolpackov
Hi Scott, Cantor, Scott canto...@osu.edu writes: I don't either, but to be blunt, the branch shouldn't be in the state it's in if you think it needs that much testing, because if a security issue pops up, you don't have the luxury of taking a lot of time. I completely understand your

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Cantor, Scott
On 2/17/15, 4:00 PM, Boris Kolpackov bo...@codesynthesis.com wrote: As far as docs go, I obviously need specifics. You will have to go through the website docs and figure what needs updating. If something specific is unclear, ask and I will try to help. But don't expect me to provide a

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Cantor, Scott
On 2/17/15, 4:41 PM, Cantor, Scott canto...@osu.edu wrote: Is this the document mentioned earlier? http://svn.apache.org/viewvc/xerces/c/admin/release-procedure.txt If you could at least skim it for any errors, that would be a big help. Never mind, I missed the note at the top, from you in

unsubscribe

2015-02-17 Thread Kevin Hoyt
please

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Cantor, Scott
On 2/17/15, 9:01 AM, Boris Kolpackov bo...@codesynthesis.com wrote: What about other platforms?! If this class is defined in a public header (i.e., a header that is installed) and the function is virtual, then this is an ABI change. It's a struct, in an impl/ header marked as do not use, and the

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Cantor, Scott
On 2/17/15, 9:10 AM, Boris Kolpackov bo...@codesynthesis.com wrote: I've reviewed all the resolved issues against the trunk, and backported 15-20 or so to the branch. Once I have access I'll commit. Before you do this have someone review your back-ports to double check there are no ABI

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Cantor, Scott
On 2/17/15, 9:07 AM, Boris Kolpackov bo...@codesynthesis.com wrote: I definitely don't have the cycles for a beta and it wouldn't fit my timeline anway. Then you shouldn't be making the release. No, I shouldn't, but I didn't see any real alternative either. If somebody else is going to, I

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Boris Kolpackov
Hi Scott, Cantor, Scott canto...@osu.edu writes: It's been years, Boris. I think you're being very aggressive here with somebody trying to help and able to do so only within the limits of his own funding and project needs. That's how this stuff works. If you're going to set requirements

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Boris Kolpackov
Hi Scott, Cantor, Scott canto...@osu.edu writes: Correction, it's not an ABI change, the pool entry class isn't exported on Windows... What about other platforms?! If this class is defined in a public header (i.e., a header that is installed) and the function is virtual, then this is an ABI

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Boris Kolpackov
Hi Scott, Cantor, Scott canto...@osu.edu writes: I definitely don't have the cycles for a beta and it wouldn't fit my timeline anway. Then you shouldn't be making the release. I'm on VC10 for my builds, and I believe those are already there. What about other users of Xerces-C++? When we

Re: Next release (was RE: [jira] [Resolved] (XERCESC-2043))

2015-02-17 Thread Boris Kolpackov
Hi Scott, Cantor, Scott canto...@osu.edu writes: I've reviewed all the resolved issues against the trunk, and backported 15-20 or so to the branch. Once I have access I'll commit. Before you do this have someone review your back-ports to double check there are no ABI breakages. Boris