You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-users@xalan.apache.org by da...@us.ibm.com on 2003/12/11 18:14:44 UTC
[VOTE} Xalan 1.7 release plan
Hi folks,
It's time to start thinking about doing a Xalan-C release
that is compatible with the latest Xerces-C 2.4 release.
Since Xalan-C 1.6 we've:
- almost completed the message localization feature (a few more tweaks
are necessary -- the patches are waiting to be committed)
- enhanced the Unix build/package/install process
- added some more EXSLT functions,
- updated the source to build with Xerces-C 2.4, and
- fixed various reported bugs.
We have a bit more work to do before we're ready to go. Recently
we've had the help of Dmitry Hayes, Matthew Hoyt, June Ng and
Soheila Bashardoust-Tajali, and we're counting on their continued
support.
There are a few bugs we still need to have a look at [Dmitry/Matt].
We also need to update the documentation [June], build the
distributions and complete the testing [June/Soheila].
So, how about we target to code freeze on January 6, 2004 and release
Xalan-C 1.7 on January 9, 2004? Does this sound reasonable to all the
committers?
If anyone else would like to volunteer their services, please let us
know. We need someone to try a MacOS build with the latest code in
cvs and flush out any build/runtime problems as we don't have an
environment ourselves to do this work.
Thanks!
Dave
Re: [VOTE} Xalan 1.7 release plan
Posted by Berin Lautenbach <be...@ozemail.com.au>.
David,
+1 from me. (Xerces 2.4 build would be a very good thing.)
I can do Net/FreeBSD testing of release archives if that's of use?
Cheers,
Berin
david_n_bertoni@us.ibm.com wrote:
>
>
>
> Hi folks,
>
> It's time to start thinking about doing a Xalan-C release
> that is compatible with the latest Xerces-C 2.4 release.
>
> Since Xalan-C 1.6 we've:
> - almost completed the message localization feature (a few more tweaks
> are necessary -- the patches are waiting to be committed)
> - enhanced the Unix build/package/install process
> - added some more EXSLT functions,
> - updated the source to build with Xerces-C 2.4, and
> - fixed various reported bugs.
>
> We have a bit more work to do before we're ready to go. Recently
> we've had the help of Dmitry Hayes, Matthew Hoyt, June Ng and
> Soheila Bashardoust-Tajali, and we're counting on their continued
> support.
>
> There are a few bugs we still need to have a look at [Dmitry/Matt].
> We also need to update the documentation [June], build the
> distributions and complete the testing [June/Soheila].
>
> So, how about we target to code freeze on January 6, 2004 and release
> Xalan-C 1.7 on January 9, 2004? Does this sound reasonable to all the
> committers?
>
> If anyone else would like to volunteer their services, please let us
> know. We need someone to try a MacOS build with the latest code in
> cvs and flush out any build/runtime problems as we don't have an
> environment ourselves to do this work.
>
> Thanks!
>
> Dave
>
>
Re: [VOTE} Xalan 1.7 release plan
Posted by June Ng <ju...@ca.ibm.com>.
This is part of the Message Localization work that was put in recently.
The LocalMsgIndex.hpp file is generated during the build - that's why it's
not in CVS.
How are you building Xalan?
Cheers,
June K. Ng
XSLT Development
IBM Toronto Laboratory
Phone: 905-413-3422 T/L: 969-3422
Email: june@ca.ibm.com
Han Ming Ong <ha...@apple.com>
12/15/2003 01:46 PM
Please respond to
xalan-dev
To
xalan-dev@xml.apache.org
cc
Subject
Re: [VOTE} Xalan 1.7 release plan
On Dec 11, 2003, at 9:14 AM, david_n_bertoni@us.ibm.com wrote:
> Hi folks,
>
> It's time to start thinking about doing a Xalan-C release
> that is compatible with the latest Xerces-C 2.4 release.
>
...
... [snipped]
...
> If anyone else would like to volunteer their services, please let us
> know. We need someone to try a MacOS build with the latest code in
> cvs and flush out any build/runtime problems as we don't have an
> environment ourselves to do this work.
While I'm doing some stuff on Xerces, I can try to help build Xalan as
well. As of today, I tried to upgrade the current Project Builder to
the new Mac OS X IDE Xcode. There is a problem: while compiling, Xcode
complains that it couldn't locate LocalMsgIndex.hpp which is referenced
in XalanMessageLoader.hpp.
I couldn't find LocalMsgIndex.hpp on the CVS file system as well. A
quick search on the current bug list reveals nothing about it.
Anyone?
thanks, Han Ming
Re: [VOTE} Xalan 1.7 release plan
Posted by Han Ming Ong <ha...@apple.com>.
On Dec 11, 2003, at 9:14 AM, david_n_bertoni@us.ibm.com wrote:
> Hi folks,
>
> It's time to start thinking about doing a Xalan-C release
> that is compatible with the latest Xerces-C 2.4 release.
>
...
... [snipped]
...
> If anyone else would like to volunteer their services, please let us
> know. We need someone to try a MacOS build with the latest code in
> cvs and flush out any build/runtime problems as we don't have an
> environment ourselves to do this work.
While I'm doing some stuff on Xerces, I can try to help build Xalan as
well. As of today, I tried to upgrade the current Project Builder to
the new Mac OS X IDE Xcode. There is a problem: while compiling, Xcode
complains that it couldn't locate LocalMsgIndex.hpp which is referenced
in XalanMessageLoader.hpp.
I couldn't find LocalMsgIndex.hpp on the CVS file system as well. A
quick search on the current bug list reveals nothing about it.
Anyone?
thanks, Han Ming
RE: [VOTE} Xalan 1.7 release plan
Posted by Mark Weaver <ma...@npsl.co.uk>.
> Hi Mark,
>
> I apologize again for forgetting about this _again_. I wanted to
> make some
> changes so that it can be more flexible than it is, and also, I can't
> really see the utility in having a dynamic result tree fragment
> option when
> node-sets are more powerful. Do you agree? Would it be OK if I tried to
> re-write your patch so we no longer support RTFs? The other enhancement I
> wanted to make is to allow for creating node-sets that contain
> things other
> than just a document node.
>
Yes, that's fine. It sounds very sensible. I'm pretty sure that the only
reason that it supports RTFs is because you asked me to put that in though
:)
> One problem is that I am travelling for most of this month, and will have
> many interrupts. If your patch can be applied pretty cleanly, I may have
> time to work it in when I can.
>
It might have bitrot, so I'll do another one against CVS (won't be until
Monday or Tuesday) and send that along.
Mark
RE: [VOTE} Xalan 1.7 release plan
Posted by da...@us.ibm.com.
Hi Mark,
I apologize again for forgetting about this _again_. I wanted to make some
changes so that it can be more flexible than it is, and also, I can't
really see the utility in having a dynamic result tree fragment option when
node-sets are more powerful. Do you agree? Would it be OK if I tried to
re-write your patch so we no longer support RTFs? The other enhancement I
wanted to make is to allow for creating node-sets that contain things other
than just a document node.
One problem is that I am travelling for most of this month, and will have
many interrupts. If your patch can be applied pretty cleanly, I may have
time to work it in when I can.
Thanks!
Dave
"Mark Weaver"
<mark@npsl.co.uk To: <xa...@xml.apache.org>
> cc: (bcc: David N Bertoni/Cambridge/IBM)
Subject: RE: [VOTE} Xalan 1.7 release plan
12/11/2003 06:03
PM
> Subject: [VOTE} Xalan 1.7 release plan
Any chance of my dynamic nodeset builder being added in?
RE: [VOTE} Xalan 1.7 release plan
Posted by Mark Weaver <ma...@npsl.co.uk>.
> Subject: [VOTE} Xalan 1.7 release plan
Any chance of my dynamic nodeset builder being added in?