Re: Xerces-C / Patch Release Request
Boris, Are there enough new features in the trunk to warrant a 3.2 release? Just adding support for a new platform should not be considered a feature. This is why I suggested a 3.1.2 patch release. I am building and testing xerces-c from the trunk on the following platforms: VC7.1 VC8 VC9 VC10 VC11, Linux G++ 4.4.5, and FreeBSD 9. The version.incl in the trunk should probably reflect the target version being planned. Sincerely, Steven J. Hathaway Apache Xalan-C --- Hi Steven, shath...@e-z.net shath...@e-z.net writes: I would like to see a patch release for Xerces-C (XML Parser). The current version of Xerces is 3.1.1. I propose a patch release of Xerces-C as 3.1.2. A bugfix release (e.g., 3.1.2) would normally be released to fix something, not to add new features. So I think we should aim for 3.2.0 (from trunk). Tasks: * Update the version.incl file * Merge the trunk to the 3.1 branch * Perform quality assurance testing on the 3.1 branch * Update the Xerces-C website documents * Package the distributions * Submit the distribution artifacts to the mirrors * Announce a patch release I wish it were that easy ;-). A (possibly incomplete) list of release tasks can be found here: http://svn.apache.org/viewvc/xerces/c/admin/release-procedure.txt?view=log The major ones are: - Test on all the platforms/C++ compilers that we claim to support - Build binaries for all the platforms/C++ compilers that we claim to support - Update (brain-dead) Xerces-C++ website management system I also remember last time I did a release, Apache infra people told me that it was the last time we were able to publish our binaries (I think it were the binaries) that way and we would have to change to the new way with the next release. Not sure what that would involve. Overall, Xerces-C++ release is quite a tedious and often frustrating process, not something you would want to do often (which is also the reason why you would try to get it right the first time). I can offer some assistance at getting the Xerces-C patch release ready for distribution. I was hoping to find time and make a release around June or July. It would also be a good idea to spend some time and try to fix some new bugs that have been uncovered since the 3.1.0 release. Not sure if you would like to wait or if you want to press ahead. But your help would be greatly appreciated. Boris -- Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog Compiler-based ORM system for C++ http://codesynthesis.com/products/odb Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
On 04/11/2013 12:59 PM, shath...@e-z.net wrote: On 4/11/13 12:35 PM, shath...@e-z.net shath...@e-z.net wrote: I don't do Debian, but those packages exist, and that is the manner in which Debian users want and need to get the software. Binaries just don't fly. I can check with Debian and Ubuntu integration teams to see what support there is to create (.deb) packages for their distributions. I'm the maintainer for Xerces-c in debian, and I lightly follow this list. If announcement of a release candidate were made, I could at least test the debian packages and at most upload the version to debian experimental where adventurous types could test. Once debian comes out of freeze for the upcoming Wheezy release and the next Xerces-c version is released (whichever comes last), I would upload the new xerces-c version to debian unstable. From there, it would migrate over to Ubuntu automatically. Other paths are possible but usually not necessary. --Jay - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
Hi Scott, Cantor, Scott canto...@osu.edu writes: I'm happy to spend some time testing the build on my supported platforms once it's ready to go. Yes, that would great. The more testing we can get done, the better. I would suggest as a way of perhaps reducing time commitment than actually producing binaries for other than Windows is not a great use of time. Yes, I was also thinking along those lines, especially for platforms like HPUX, AIX, etc. But perhaps you are right, maybe we should drop everything except Windows. Would be good idea to send an email to the lists and check if anyone objects. Boris - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
Thanks Boris! I will be glad to pursue the release issues, patches, documentation, and features. Expect to see more activity from me on these in JIRA. Steven J. Hathaway Hi Steven, shath...@e-z.net shath...@e-z.net writes: I would like to see a patch release for Xerces-C (XML Parser). The current version of Xerces is 3.1.1. I propose a patch relase of Xerces-C as 3.1.2. A bugfix release (e.g., 3.1.2) would normally be released to fix something, not to add new features. So I think we should aim for 3.2.0 (from trunk). Tasks: * Update the version.incl file * Merge the trunk to the 3.1 branch * Perform quality assurance testing on the 3.1 branch * Update the Xerces-C website documents * Package the distributions * Submit the distribution artifacts to the mirrors * Announce a patch release I wish it were that easy ;-). A (possibly incomplete) list of release tasks can be found here: http://svn.apache.org/viewvc/xerces/c/admin/release-procedure.txt?view=log The major ones are: - Test on all the platforms/C++ compilers that we claim to support - Build binaries for all the platforms/C++ compilers that we claim to support - Update (brain-dead) Xerces-C++ website management system I also remember last time I did a release, Apache infra people told me that it was the last time we were able to publish our binaries (I think it were the binaries) that way and we would have to change to the new way with the next release. Not sure what that would involve. Overall, Xerces-C++ release is quite a tedious and often frustrating process, not something you would want to do often (which is also the reason why you would try to get it right the first time). I can offer some assistance at getting the Xerces-C patch release ready for distribution. I was hoping to find time and make a release around June or July. It would also be a good idea to spend some time and try to fix some new bugs that have been uncovered since the 3.1.0 release. Not sure if you would like to wait or if you want to press ahead. But your help would be greatly appreciated. Boris -- Boris Kolpackov, Code Synthesis http://codesynthesis.com/~boris/blog Compiler-based ORM system for C++ http://codesynthesis.com/products/odb Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
On 4/11/13 5:03 AM, Boris Kolpackov bo...@codesynthesis.com wrote: I would suggest as a way of perhaps reducing time commitment than actually producing binaries for other than Windows is not a great use of time. Yes, I was also thinking along those lines, especially for platforms like HPUX, AIX, etc. But perhaps you are right, maybe we should drop everything except Windows. Would be good idea to send an email to the lists and check if anyone objects. For Linux it's literally a complete waste of your time, same for Mac. Solaris is the one that you can make a case for, but it's also the worst of the lot by far to deal with, and there are so many variables involved in that platform that I know it never was of any use to me in producing my software. -- Scott - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
Scott Boris, Besides windows builds with VS 2003, 2005, 2008, 2010, 2012 - I also perform builds on FreeBSD, PCBSD, and GNU Linux. I DO NOT build packages for Debian and RedHat package managers. I DO build debug and release builds of Xerces-C from sources. I can send some pings to other Xerces/Xalan developers to see if they can perform testing on their AIX and Solaris-10 platforms. I have not been successful in creating a SunStudio 12.3 environment for testing with Solaris-11. The Solaris-11 will only support a 64-bit environment. Solaris-10 supports both 32-bit and 64-bit platforms. I will gladly share my insights on this list and make postings to JIRA. Sincerely, Steven J. Hathaway Hi Scott, Cantor, Scott canto...@osu.edu writes: I'm happy to spend some time testing the build on my supported platforms once it's ready to go. Yes, that would great. The more testing we can get done, the better. I would suggest as a way of perhaps reducing time commitment than actually producing binaries for other than Windows is not a great use of time. Yes, I was also thinking along those lines, especially for platforms like HPUX, AIX, etc. But perhaps you are right, maybe we should drop everything except Windows. Would be good idea to send an email to the lists and check if anyone objects. Boris - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
On 4/11/13 12:35 PM, shath...@e-z.net shath...@e-z.net wrote: Besides windows builds with VS 2003, 2005, 2008, 2010, 2012 - I also perform builds on FreeBSD, PCBSD, and GNU Linux. I DO NOT build packages for Debian and RedHat package managers. I DO build debug and release builds of Xerces-C from sources. For Linux, it is risky in the extreme to rely on binaries built for one distro on another. I Understand! I provide RPMs for Xerces as needed on all the platforms I support that don't ship their own. If the project wanted to do that formally, I can assist with that, or it could offer a pointer to my packages at build.opensuse.org if it likes. I don't do Debian, but those packages exist, and that is the manner in which Debian users want and need to get the software. Binaries just don't fly. I can check with Debian and Ubuntu integration teams to see what support there is to create (.deb) packages for their distributions. I have not been successful in creating a SunStudio 12.3 environment for testing with Solaris-11. The Solaris-11 will only support a 64-bit environment. Solaris-10 supports both 32-bit and 64-bit platforms. Solaris-11 has also changed the way that software distribution packages are managed. I may still be able to test on Solaris-11 on X64 platforms, but I first need to get comfortable with the platform. - Steven J. Hathaway I thought I had been testing both on Solaris 11 but I can't verify that right this second. -- Scott - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
On 4/11/13 12:59 PM, shath...@e-z.net shath...@e-z.net wrote: I can check with Debian and Ubuntu integration teams to see what support there is to create (.deb) packages for their distributions. I can't speak for Ubuntu, but there are official shibboleth packages for Debian (that I don't maintain) and that includes Xerces, if it wasn't already packaged. So I may know the maintainer, and the point is that you don't do it twice. Somebody owns that responsibility and you/we/somebody can share that or assist. Solaris-11 has also changed the way that software distribution packages are managed. I may still be able to test on Solaris-11 on X64 platforms, but I first need to get comfortable with the platform. Yes, Solaris packages are historically awful and there are a dozen different packaging projects that are all different. Whether Oracle is changing that and using something new that actually works I couldn't say, but nothing that existed in Solaris alone was usable before or worth wasting the time on. -- Scott - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
Hi Steven, shath...@e-z.net shath...@e-z.net writes: I would like to see a patch release for Xerces-C (XML Parser). The current version of Xerces is 3.1.1. I propose a patch relase of Xerces-C as 3.1.2. A bugfix release (e.g., 3.1.2) would normally be released to fix something, not to add new features. So I think we should aim for 3.2.0 (from trunk). Tasks: * Update the version.incl file * Merge the trunk to the 3.1 branch * Perform quality assurance testing on the 3.1 branch * Update the Xerces-C website documents * Package the distributions * Submit the distribution artifacts to the mirrors * Announce a patch release I wish it were that easy ;-). A (possibly incomplete) list of release tasks can be found here: http://svn.apache.org/viewvc/xerces/c/admin/release-procedure.txt?view=log The major ones are: - Test on all the platforms/C++ compilers that we claim to support - Build binaries for all the platforms/C++ compilers that we claim to support - Update (brain-dead) Xerces-C++ website management system I also remember last time I did a release, Apache infra people told me that it was the last time we were able to publish our binaries (I think it were the binaries) that way and we would have to change to the new way with the next release. Not sure what that would involve. Overall, Xerces-C++ release is quite a tedious and often frustrating process, not something you would want to do often (which is also the reason why you would try to get it right the first time). I can offer some assistance at getting the Xerces-C patch release ready for distribution. I was hoping to find time and make a release around June or July. It would also be a good idea to spend some time and try to fix some new bugs that have been uncovered since the 3.1.0 release. Not sure if you would like to wait or if you want to press ahead. But your help would be greatly appreciated. Boris -- Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog Compiler-based ORM system for C++ http://codesynthesis.com/products/odb Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
Re: Xerces-C / Patch Release Request
On 4/10/13 10:46 AM, Boris Kolpackov bo...@codesynthesis.com wrote: I was hoping to find time and make a release around June or July. It would also be a good idea to spend some time and try to fix some new bugs that have been uncovered since the 3.1.0 release. Not sure if you would like to wait or if you want to press ahead. But your help would be greatly appreciated. I'm happy to spend some time testing the build on my supported platforms once it's ready to go. I would suggest as a way of perhaps reducing time commitment than actually producing binaries for other than Windows is not a great use of time. Most projects using this software need packaging, not binaries. The focus should be on making sure configure; make works well. In my opinion anyway. -- Scott - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
