* Bleeding edge technology
For example, some things that may have been included in the past that might be considered bleeding edge are things like ext4, btrfs, the original updater that evolved from red-carpet (the first one that was implemented in Mono back in the 10.x days - back when the resolver spiked CPU utilization for extended periods of time for many users), beagle, and even KDE4 (not in its current state, but when it was added to 11.2). Those technologies might at their inclusion have been considered "technology previews".
The one thing that made ext4 bleeding edge instead of a "technology preview" was making it default. Not being bleeding edge doesn't mean excluding bleeding edge software, but it does mean not using it by default or even depending on it.
Doesn't this argue for having more "repositories" (or collections of packages) and dependencies between repositories? These "technology previews" could be kept out of the core repository (and so not be seen by inexpert users) but easy to add. Having inter-repository dependencies would allow the solver to select packages from the right place (i.e. create a combination that has been tested) for additional packages required as dependencies and ignore the alternatives offered from other repositories, even if they are newer or in some other way "look better". David -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org