[sword-devel] 1.7.2 release

[Greg Hellings]

On Thu, Jan 16, 2014 at 9:35 AM, Костя Маслюк <kostyamaslyuk at gmail.com>wrote:

> > I would assume this requires a change to function signatures, so it's
> not going to appear in 1.7.x at all.
>
> In your mouth it sound like that it going never appear in Sword. Patch
> only add parameter with default value to one public function. There is no
> problem to revert and make some work in private part of class so it will be
> absolutely abi compatible.
>

This conversation has strayed far from the actual bounds of 1.7.2 release,
but I just want to say here that unless a change is both identical in API
and ABI to 1.7.0 I won't be including it in the sword-1-7-x branch. No new
functions, no changing signatures, no new classes, etc. Any changes like
that will have to wait for the next branch release. sword-1-7-x is strictly
bug-fix only.

This isn't a value judgment on the feature discussion which has taken over
this thread nor on anyone else's abilities or merits of particular patches.
It's because this is a bug fix branch and this is what was discussed and
agreed to for the 1.7 release series so that important fixes like those
already in the 1.7.1 and 1.7.2 releases don't have to wait for long periods
of vetting and maturation before becoming available to our users and
packagers.

--Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20140116/a6da1ffe/attachment.html>