Re: [sword-devel] release schedule

2003-03-06 Thread Martin Gruner
> Right, but my point was that since neither of these two new features are > complete, we should wait a bit for a release. I don't anticipate that it > will take very long to write the remainder of the OSIS filters that we > need most immediately, and I'd have them written by the end of the weeken

Re: [sword-devel] release schedule

2003-03-06 Thread Chris Little
On Thu, 6 Mar 2003, Martin Gruner wrote: > > I know you're anxious for a new release of Sword, but I don't think it has > > even been discussed before your email and I can't think of much than has > > been changed since 1.5.5a except for SWBuf and partial OSIS support -- > > neither of which are f

Re: [sword-devel] release schedule

2003-03-06 Thread Martin Gruner
> I know you're anxious for a new release of Sword, but I don't think it has > even been discussed before your email and I can't think of much than has > been changed since 1.5.5a except for SWBuf and partial OSIS support -- > neither of which are finished. Well, not sure how much has to change un

Re: [sword-devel] release schedule

2003-03-06 Thread Martin Gruner
Hm, Troy, what have I done wrong that you only have such sharp words for me? > You mean "stuff that needs to be packaged up for release" for Bibletime :) Well, not quite. make dist is supposed to make a clean and standard distribution of the sword library. All the major projects nowadays use thi

Re: [sword-devel] release schedule

2003-03-06 Thread Chris Little
On Thu, 6 Mar 2003, Martin Gruner wrote: > Er, well, why not just test/fix SWBuf now and keep OSIS for the next sword > release? That way we could concentrate on the testing stuff now and prepare > the next release soon, with better OSIS support? Wasn't it the plan to switch > to OSIS internall

Re: [sword-devel] release schedule

2003-03-06 Thread Daniel Glassey
On 6 Mar 2003 at 14:13, Troy A. Griffitts wrote: > > rather than tarring up the whole cvs tree. This way the tar.gz file only takes > > about 500K rather than 4M. It will only include stuff that needs to be > > packaged up for release. Please try it out and report any errors in the make > > pro

Re: [sword-devel] release schedule

2003-03-06 Thread Troy A. Griffitts
rather than tarring up the whole cvs tree. This way the tar.gz file only takes about 500K rather than 4M. It will only include stuff that needs to be packaged up for release. Please try it out and report any errors in the make process here. You mean "stuff that needs to be packaged up for releas

Re: [sword-devel] release schedule

2003-03-06 Thread Martin Gruner
> The current state of cvs isn't anywhere near ready for release. SWBuf > and the changes to the filters & module drivers to accomodate it haven't > been tested very thoroughly (or at all in some cases). We also need to > complete filter work for OSIS support since it is about half implemented >

Re: [sword-devel] release schedule

2003-03-06 Thread Chris Little
On Thu, 6 Mar 2003, Martin Gruner wrote: > First of all, I want to congratulate Troy and all who helped to the great > changes in the lib that SWBuf brought about. This will make sword more stable > and less memory consuming. Awesome work, guys. > > Is there a release schedule for 1.5.6? I alre