new version of supertux

[Steven Pritchard]

There is a new version of supertux out.  The announcement is here:

http://lists.berlios.de/pipermail/supertux-devel/2006-December/001338.html

You should be able to install it from extras-development now.  (It
installs fine on FC6 for me.)  Upstream doesn't consider this a
"stable" release, but if it seems to be working well for everyone, I'm
tempted to push an update for FC6.

Feedback appreciated on this bug:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220665

Steve

[Michael Thomas]

Steven Pritchard wrote:
> There is a new version of supertux out.  The announcement is here:
>
> http://lists.berlios.de/pipermail/supertux-devel/2006-December/001338.html
>
> You should be able to install it from extras-development now.  (It
> installs fine on FC6 for me.)  Upstream doesn't consider this a
> "stable" release, but if it seems to be working well for everyone, I'm
> tempted to push an update for FC6.
>
> Feedback appreciated on this bug:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220665

As I just wrote in bugzilla, I would avoid upgrading this for FC6 if 
there are any savefile or config file compatibilty problems upgrading 
from the current FC6 version to 0.3.0.  I managed to irritate a few 
people when I bumped prboom from the 2.3 series to 2.4 in FC6 because of 
save/config file incompatibilities.

--Wart

[Jason L Tibbitts III]

> > > > > "MT" == Michael Thomas  writes:

MT> As I just wrote in bugzilla, I would avoid upgrading this for FC6
MT> if there are any savefile or config file compatibilty problems
MT> upgrading from the current FC6 version to 0.3.0.

I have to agree; I've avoided bumping nazghul in the release branches
due to savefile incompatibilities.  (I'm only guessing as to the
number of people who might actually have it installed though; my
best estimate is about three or so.  Smolt, save us!)

If you do update devel, make sure to get something into the release
notes.  The simplest way seems to be to include "*docs*" in your
commit message and write in the release note.

- J<