Understood going forward.
There were a few factors which made this a slightly non-standard
situation. First, this wasn't exactly a bug fix. It was a workaround
for a bug in a version of libcurl. I was hoping libcurl would be
patched. And no, I personally didn't report the issue to the curl team,
which I should have. Secondly, one of our frontend projects submitted a
small update which changed something another of our frontends depended
on. The second project had updated their code to still work with the
new change, but they hadn't released yet. If they had released then
everyone would be happy with us releasing SVN as is. As it stands right
now 1 of the 2 projects will need to patch SVN for their frontend to
work. So delaying was a hopeful but unfruitful exercise. It was a
choice we made to with the best information we had at the time.
All this to say, sometime the situation is a little more complicated
than shear negligence, so please be kind when asking for a release.
We're planning to release 1.6.2 probably next week so I hope this is
quick enough.
Troy
On 9/14/2010 11:46 AM, Manfred Bergmann wrote:
Am 14.09.2010 um 11:19 schrieb Martin Gruner:
Hi Karl,
branching is not a pain for this kind of purpose. Just branch off the
repository state of 1.5.1 (I guess there is a tag available), apply the
one-liner, and release a 1.5.1.1. A bugfix release. That should have
been the answer to the problems at hand, not a patch.
Right.
Implement new features in trunk. Apply bug fixes to trunk and to a 1.6.1 branch
or tag as well.
No worries then about being forced to release untested new features for a bug
fix release.
Manfred
Am 14.09.10 11:58, schrieb Karl Kleinpaste:
Jaak Ristioja<risti...@gmail.com> writes:
Why not branch?
Because branching is a whole new world of pain, for something as
straightforward as a workaround patch for a curl library bug. It's a
one-line patch, for pity's sake.
Since there has probably been no announcement from Sword that distros
should patch,
Um... Procession from false assumption. Anyone who's involved enough
to be doing distribution of Sword software ought to be involved enough
to be seeing discussion about such things as the curl bug and its patch
here.
When the bug was encountered, there was rather a lot of activity about
it. Anyone who didn't see it...just wasn't watching.
If I remember correctly, an OpenSUSE user was the last to report the
bug to BibleTime, so maybe OpenSUSE still has it unpatched.
No. Brian Dumont<bdum...@ameritech.net> is on top of that, and has
informed me in the past that appropriate updates were available as of
Aug 05.
Whether updated builds get to the field properly is a whole different
question -- e.g. we have the annoying nightmare that a Xiphos display
workaround release for an xulrunner bug, fixed in May, hasn't gotten
back to Ubuntu repositories, though it's available elsewhere just fine
(via CrossWire's Ubuntu PPA for Sword builds).
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
