I started looking at the gnustep ebuilds and doesn't it make more sense to have their KEYWORDS value set to match what the GNUSTEP developers themselves label their builds as? For example, gnustep-back is officially the stable version from www.gnustep.org yet the 0.8.3 ebuild is listed as stable. This is pretty much true of all of the gnustep packages.
I belive that the keywords will remain unstable until the package is proven to be stable as a part of a _Gentoo_ system. Even if the source itself is stable, it needs to work well with the rest of Gentoo before it's listed as stable. I'm not sure who decides when that is, though.
i'm reassigning this back to bug-wranglers for a true gnustep maintainer
As a FULL gnustep environment including the non-console devel apps such as gorm requires the "unstable" tree, the "unstable" packages are better off being our "stable".. I currently have a console-only system to devel on... soon I will have a system with X capabilities and I will get the gnustep packages up to date.
I don't have time to look at the gnustep/windowmaker stuff at the moment :(
gnustep-{make,base}-1.6.0 and gnustep-{gui,back}-0.8.5 are updated, in portage, and marked stable. Coinciding with gnustep's current stable releases.
