Hi John,
welcome aboard ;-)
John Snelson wrote:
Hi everyone,
I'm looking forward to Xerces-C 3.0 - not least because the build
system seems to have been markedly improved :-). I'm happy to do some
build testing, although I have to look into what platforms I have
available to me. Shall I just add my results to the wiki page?
Sure; we have have split the page into two separate pages, one for the
official platforms, and one for the less used/less tested ones.
Also, can someone tell me how to run the tests?
Running "gmake check" will build the tests and automatically run the
sanityTest suite, checking it against the expected result.
Alberto
Also I've got some patches that fix a couple of bugs, but I'm trying
to get legal approval to sign the contributor agreement. The patches
cover the following:
1) Modify socket and winsock net accessors to use an extensible buffer
(avoids possibility of HTTP headers not fitting in the fixed size
buffer), share HTTP generating and parsing code, make the
"Content-Type" header available (needed for correctly identifying the
encoding of an XML file), and fix a Windows 64 bit compilation problem
(SOCKET is a 64 bit pointer on Windows 64).
2) Fix general memory manager issues in RegularExpression, bugs in
RegularExpression::replace(), and add a more general purpose
RegularExpression::allMatches() method (needed for XQilla to support
XSLT 2.0's analyze-string functionality).
John
Gareth Reakes wrote:
That all looks great to me Boris. Thanks for driving this forward. I
am happy to help on any of these tasks. Would anyone who can offer
any help (anything from docs to code) please speak up. 3.0 has been a
long while coming and it will be great when we finally get it out!
If you want a bug fixed for 3.0 please follow the process Boris has
suggested. Telling us you want a bug fixed the day before we are
going to release 3.0 will result in it not happening!
Gareth
On 22 Feb 2008, at 13:05, Boris Kolpackov wrote:
Hi,
I am trying to figure out what needs to be done in order to release
3.0.0. I've created a few new and marked a number of existing bugs
as scheduled for 3.0.0 which can be viewed using the following query:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10510&fixfor=12312833
If you would like to see a particular bug fixed in 3.0.0 and is willing
to work on the fix then feel free to schedule it for 3.0.0 as well (add
3.0.0 to the "Fix Versions" field).
There are two major chunks of work that still need to be done (marked
as blockers). The first is making sure the code builds, passes tests,
and installs on all supported platforms. The second is website and
documentation changes needed to support both Xerces-C++ 2 (2.8.0)
and 3 (3.0.0)-series.
For the website/documentation changes I have outlined a plan in this
bug report:
https://issues.apache.org/jira/browse/XERCESC-1784
Please add your thoughts as comments there.
For the build/test/install status of the supported platforms refer
to this Wiki page:
http://wiki.apache.org/xerces/XercescBuildStatus
There is also a bug report for tracking this task:
https://issues.apache.org/jira/browse/XERCESC-1785
Boris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Gareth Reakes, CTO WE7
+44-20-7117-0809 http://www.we7.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
