I will not -1 it, but hear me out ;) I don't know jxpath (seen it around though), but just took a look at the sourcecode. It has about 8 testcases and that is a huge difference with the actual number of classes in the jxpath package. How can you asure that in the next release current behaviour is not breaking bacward compatibility, except for the fact that you can say "I seen it work" ? And of course the current release can have many bugs, which can only be revealed in testcases (not saying it is, don't get me wrong..)
Mvgr, Martin On Sun, 2002-06-16 at 16:19, Dmitri Plotnikov wrote: > I'd like to call for a release vote on JXPath 1.0 . It has been stable for > a while, and there are no outstanding bugs against it. All the goals we had > initially stated for this release have been met. > > The release candidate build is > > http://jakarta.apache.org/builds/jakarta-commons/release/commons-jxpath/v1.0 > > +1 (this is my vote) > > Thank you, > > Dmitri > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
