From: Thomas Mills Hinkle <tmhinkle@gm...> - 2006-09-04 01:21:25
So as I've mentioned before on this list, I've generally made a
mistake by creating the "unstable" branch and letting the "stable"
branch go without maintenance in the meantime. Having realized that my
ability to maintain two radically different branches is quite limited,
I've been planning for a longtime to re-merge -- and I'm ready to
release a "stable" release as an 0.12 series. Note that "stable"
doesn't mean too much -- I'm pretty confident the last several
"unstable" releases have been more stable than the stable branch was
So, this is a call for testing so that we can fix any absolute
show-stoppers. If I don't see any absolutely horrible bug reports,
I'll go ahead and rename 0.12.0.pre1 to 0.12.0 and release it as
"stable" at the end of the week.
Known issues/things you might be able to help with or give feedback on
are listed below.
* I've gone back to producing RPM packages for the convenience of
users on those distros. I don't expect these packages to be as good as
official ones -- but I think that having a package makes
installation/uninstallation easier. Obviously that's not the case if
the packages are completely broken -- so if those of you on RPM
systems could let me know if the packages work, that would be nice.
* The latest unstable release now includes a windows installer for the
first time in ages -- hopefully it works. I know that at present the
main gourmet window closes with an error -- as far as I can tell
there's no actual problem with the program -- just something wrong
with the packaging-up as an executable that's causing windows to
believe Gourmet has died badly. If anyone has more knowledge of the
windows side of thing and can look into this, it would be nice to fix
this before calling the release "stable."
A final note -- I fixed the sort order in the latest release as per
the previous thread.