[sword-devel] I implore you...
Troy A. Griffitts
scribe at crosswire.org
Sun Jun 9 13:21:43 MST 2013
I don't think other developers are getting ignored. Please be
specific. Just because I don't accept a patch doesn't mean a developer
is getting ignored.
In fact, many times trying to make this release, when people complain
that we need something fixed for this release, I ask for a simple
testsuite addition to show the problem and desired result, and don't get
I don't believe the problem is as you think it is Jaak. Many people
whine about this or that. Not all whine for things to go in the same
Everyone whines for a release but not everyone is willing to help submit
tests and then fixes for those tests.
You stated that you would get involved to help, but you only submit
things for which I previously told you I wasn't interested in accepting
(worrying about pedantic warnings whose changes often make the code less
readable and do nothing to improve any of the real problems for the end
user. Though I do appreciate a few of the warning fixes you submitted,
a few being actual bug fixed too (thank you)-- I'm just ranting right now.)
I have no excuses, but neither does anyone else.
End of rant.
On 06/09/2013 09:56 PM, Jaak Ristioja wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 09.06.2013 18:09, Greg Hellings wrote:
>> ...please just release 1.7.0 now. 15 months ago Troy promised it
>> would be released the following month. Some things have happened
>> that made it a bit difficult, but 15 MORE months beyond the
>> already-too-long time is ridiculous. Please just release it as it
>> is and then make regular bug-fix releases to address each of these
>> outstanding bugs.
>> Please, stop with the "one more bug" or "one more thing" or "next
>> week/month, I promise". Just release it. Xiphos is unable to make
>> a new release because it has been repeatedly promised that "very
>> soon now" a new Sword would be released, so the application has
>> committed to the current SVN of Sword. BibleTime has support for
>> several of the existing Sword features in a development branch but
>> cannot make a release with that support because of a commitment to
>> only supporting released Sword versions.
>> Troy, you've said one reason you procrastinate releases is because
>> you don't like going through the release process. I've offered
>> twice now - with no response - to manage a stable branch of the
>> library and make regular bug-fix releases from that while main
>> trunk development continues onwards. With git, I already maintain
>> such functionality on the github mirror of CrossWire - doing it for
>> a stable branch would not be more difficult. Maybe someone else
>> would also be willing if you don't want me to do that.
>> But please, can we just have a release? 'Twould be nice.
> I second that.
> And it's just getting ugly that other developers are being ignored in
> many matters regarding the Sword library.
> Lately, I've been thinking about this many times. The way I see it,
> unless the situation for this community changes rapidly for the better
> this summer, the next feature-release of BibleTime will probably link
> exclusively against a fork of the Sword library. We also hope to
> cooperate with other Sword projects in this matter.
> This is not meant as a personal offense towards Troy or others. But if
> our attempts to influence a release of a new version of Sword keep
> failing, the rest of the community must take decisive action
> themselves. We'd rather not fork, so please mitigate this. The clock
> is ticking.
> Everyone, please consider praying on these matters.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> -----END PGP SIGNATURE-----
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel