Comment 16 for bug 287158

Gerfried Fuchs wrote:
> I haven't done a direct diff, but usually wesnoth has strict guidelines
> for their stable updates: There won't be any feature changes at all
> because a stable release has to be compatible with every other patch
> update to it. So, most of the times, the only changes are to the
> translation files and bugfixes for crashes in campaigns or in gameplay
> that don't expose a different behavior that would result in an OutOfSync
> situation for multiplayer games (see LP #256345 for a story in this).

I see. Definitely it's something to consider for the future. This time I just
backported the fix though.

[split]
> I am not trying to convince you to push those in, especially since I
> reworked a bit on the packaging end, too, especially in the 1.4.6-1
> upload, even though that would close a LP bug:

But that bug means renaming a binary package, which is a no-go for a stable
release. In any case, I'd update the package to 1.4.7 but using the same packaging.

> So save bet is to just pick the bugfix, even though I guess that some
> might disagree with it because technically it's "just" an upstream
> stable release update with pretty tight rules in that respect - to some
> degree possibly compareable to the postgresql updates within their 8.3
> branches and so on.

For that, a general permission needs to be given from the Technical Board (one
for the package, then every new upstream stable release can be uploaded), so
perhaps we can consider it for the future. Will have to think about it.

> Hope that deeper insight helps a bit. :)

It surely does, thanks a lot!

Best regards,
Emilio