I have created two new experimental projects: GNOME:GTK:STABLE GNOME:GTK:Factory
They contain the latest stable packages (newer than 11.0) and latest Factory packages. They are intended to become primary gtk+ repositories in the future.
They are intended for build of packages, which need it (e. g. gimp-unstable). Later they may be used for building of GNOME:STABLE.
However 100% of builds succeeded, for <= 10.2 these packages cannot be used in rebuilds due to libtool problem.
I think that splitting of GNOME:STABLE in the same way would be a good idea. Large repositories with lots of introduced dependencies are hard to maintain and cause unexpected breakages of other packages.
Using of repo path and base repo features would help to create easy to install repositories without a lot of unneeded packages. People can then control their rolling updates better.
As I wrote before, I would like to see: GNOME:GTK:STABLE based on openSUSE:* GNOME:GTK:Factory based on openSUSE:* GNOME:STABLE (packages with GNOME release cycle) based on GNOME:GTK:STABLE GNOME:Factory (packages with GNOME release cycle) based on GNOME:GTK:Factory GNOME:Applications (Factory snapshot of applications) based on GNOME:STABLE (or GNOME:Factory if it will be required) GNOME:Community (packages not connected with Factory) based on any repository multimedia:gstreamer based on GNOME:GTK:STABLE and openSUSE:* GNOME:rebuilds (package copies for <= 10.2 just for rebuild with packages in a new prefix.) based on GNOME:STABLE and maybe GNOME:GNOME++, GNOME:GALAGO...