njakes The way I wanna go about it is having a "beta" branch + set of packages people can test out when it's ready, and I do intend on having testing images for folks (plus we'll need them internally, so win-win).
I want to take the same path with the Software Center too, where you can install the new Software Center as a "beta" to start testing whatever is there (for example, it might start before sol is even done so we can test the other plugins), but still have the old one around for normal eopkg operations. Then once bugs are worked out and sol is integrated, all we gotta do to roll it out completely is update the main solus-sc repo package.
