[sword-devel] progress with 1.7.0 ?
mark at foresightlinux.org
Tue Jun 4 02:27:17 MST 2013
Putting on my packagers hat, I would ask to just fix critical bugs and
regressions from 1.6 and throw out 1.7.
Create a 1.7 branch and do bugfixes for 1.7 on that and push every new
feature to trunk (or do them in branches that get merged back to
As packager Itend to avoid packaging random revisions of trunk, not
knowing what may be broken. But to gt new features of
bibletime/xiphos, you name it, I will at some point need t do just
And adding to this, for interest people stopping by at crosswire.org,
not having a release for about 2.5 years makes sword look abandoned
although it isn't.
Taking off that packagers hat again and moving back to patiently waiting...
On Mon, May 27, 2013 at 4:31 AM, Nic Carter <niccarter at mac.com> wrote:
> Heya all,
> Just wondering where we're up to with 1.7.0? A couple of questions about it:
> - default compiler settings for iOS (under Xcode) enable certain warnings. These caused the thml filters to throw a couple of hundred encoding warnings, and so I applied the patches that were emailed to the list last December and squashed them all. Was very cool. Did we have plans to apply those patches to SVN? As I keep my own copy of SVN inside my PocketSword HG this works fine for me, but how about for others? :)
> - We have been talking about something along the lines of checking if a book is empty or not and incorporating that into the library. Is that a possibility for 1.7.0? Or is it more realistic for me to incorporate it into my Obj-C code for PocketSword and Eloquent? It seems several front-ends have this code already in them, so is it a matter of taking that and pushing it down into the lib or should we each implement it ourselves in the front-end code?
> - It's cool seeing updates to the filters :) I was asked a while ago to implement the OSIS "underline" tag for underlining text. Is this something we wanted to incorporate into our filters or did I jump the gun and support an unsupported or deprecated tag? :) It was as easy to implement as the "super" and "sub" tags that Troy recently added. :)
> Thanks heaps, ybic
> nic... :)
> PS: as usual, let me know what I can do to help with this stuff progressing. :) Tricky with lack of time, as with everyone else here :)
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
Foresight Linux Xfce Edition
Cause your desktop should be freaking cool
More information about the sword-devel