+1 for Xalan 2.7.1 release. Christine Li XSLT Development IBM Toronto Lab Tel: (905)413-2601 Email: [EMAIL PROTECTED]
Brian Minchau/Toronto/[EMAIL PROTECTED] 08/08/2007 01:34 AM Please respond to xalan-dev@xml.apache.org To xalan-dev@xml.apache.org cc Subject [VOTE] Xalan 2.7.1 release This is a call on the Xalan PMC members to vote on a new Xalan-J 2.7.1 release. The tag for the proposed release is in subversion at http://svn.apache.org/repos/asf/xalan/java/tags/xalan-j_2_7_1 The PMC members to vote are: Brian Minchau Christine Li Dmitry Hayes Henry Zongaro John Gentilin Ramesh Mandava Santiago Pericas-Geertsen 75% (i.e. 6 of the 7) of the PMC members need to vote +1 Besides the usual bug fixes the PMC members should take note that JIRA issue XALANJ-2358 has been fixed, which are some updates to meet the requirements of the Apache 2 license. PMC members should look at http://www.apache.org/dev/apply-license.html. Specifially for XALANJ-2358 there is now a single LICENSE.txt file that is a collection of license information (as required by http://www.apache.org/dev/apply-license.html). Likewise there is a single NOTICE.txt file that is a collection of older notice and readme information files. The fix in XALANJ-2358 also modified the build.xml file to include the new files NOTICE.txt and LICENSE.txt to be included in the top level directory of the distribution zip files (or equivalent). So I think we are OK on the Apache 2.0 licensing points. As for quality, the test buckets will run and the quality will be as good as before with no major regressions for this proposed release to be acceptable. I won't consider fixing any last minute issues as needing a re-vote on the release. I propose that the code in subversion at http://svn.apache.org/repos/asf/xalan/java/tags/xalan-j_2_7_1, or that code with minor bug fixes, be the code for the Xalan-J 2.7.1 release. I vote +1 - Brian Minchau --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
