Xalan PMC, you have my support!
Committee Information:
There are still significant JIRA issues that need minor work or need to
be closed relating to Xalan-C version 1.11. As I work on the product
documentation, I will also try to address the outstanding JIRA issues.
There are a few that are significant patches that need to be made to the
Xalan-C trunk. I'll research the critical issues and report back to
this list.
If the review process is not stalled, I should have a completed
Xalan-C/C++ version 1.11 user guide ready in September 2011. The bulk
of the work should be completed sometime in August 2011.
Again, I give thanks to the reformed Xalan PMC. There are some
infrastructure details that need to be handled in order to publish a new
release of Xalan-C.
As for managing the xalan/c repository, I have some items for discussion.
The xalan/c/<trunk> currently serves numerous customers that use the
Xalan-C v.1.11 snapshots in their products. The <trunk> should be
maintained for this support until Xalan-C v1.11 is officially released
as a product and posted on the ASF mirrors.
Xalan-C Version 2 should be on an xalan/c/<branch> for development until
after Xalan-C v1.11 is released. When Xalan-C v2.0 has some usability
and version 1 has no further development, then Version 2 can be moved to
the <trunk> and patches to Version 1 can be done in a <branch>.
Binary Package Builds:
I can create binary packages builds for Microsoft VS-2003, 2005, 2008,
and possibly 2010. I might even be able to restore old Microsoft MSDN
software to create a binary package for Visual Studio (VS6).
I can create binary packages on Debian Linux. I don't have Red Hat
package management tools. One of my co-workers has BSD unix on several
virtual machines.
I have vendors that maintain software on IBM Z-OS mainframes, AIX on
RS-6000 clusters, IBM AS400, and Linux on IBM mainframes. I don't know
of their programming staff resources that they might contribute to the
effort.
I have a vendor that maintain system software for HP-UX on the HP RISC
fault-tolerant clusters.
I know of vendors that maintain software on Solaris systems, but am
unclear on their programming skills. Many years ago I created and
maintained software using the Solaris package management tools.
Any committers willing to provide binary packages for evaluation would
be welcome to participate.
Sincerely,
Steven J. Hathaway
P.S.
A Research Project: I am trying to design a high-performance engine
that operates as a stand-alone XML document transformation appliance. A
library of stylesheets are to be cached in a compiled state. The
incoming connection would supply an XML document and identify a
stylesheet for transformation. The outgoing communications would be the
transformed document or indicate a set of errors found in the
transformation. I am still researching the architecture requirements
and the capabilities of existing development efforts.
Some of my future transformation requirements can be massive. Several
families of XML schemas define 86,000 to 180,000 distinct elements
catalogued into numerous namespaces. I see in the near future that one
XML family in the US Dept. of Justice will embrace over 400,000
cataloged elements in a family of XML schema definitions. This also
requires massive stylesheet capability to accommodate the related
transformations. In such a system, I see the need to be able to perform
5-40 transformations per second (with parallel operations).
========================
Bertrand Wrote:
Hi Xalan community,
I'm pleased to announce that the ASF board has voted for re-establish
the Xalan PMC as follows:
* David Bertoni (dbertoni, PMC chair)
* Gareth Reakes (gareth)
* Tim Williams (twilliams)
* Sanjiva Weerawarana (sanjiva)
* Gary D. Gregory (ggregory)
* Michael Glavassevich (mrglavas)
* Bertrand Delacretaz (bdelacretaz)
Existing PMC members (apart from David who was the only active one
left) have been discharged from their PMC responsibilities. If any of
those folks want to become active again they're more than welcome, of
course.
= =
Also, I think a special report should be prepared for the next board
meeting, on July 20th, to get back on track with those reports.
Thanks,
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
