Begin development of ypkg 3.
Continue development of ypkg 3.
Officially (re-?)start development of Budgie 11. This development will occur internally on our Development Tracker until it is in a more ready state, in which case it will be available under our GetSolus GitHub organization. This will enable us to iterate on Budgie 11 at a pace which won’t compromise our other higher priority and more time sensitive development efforts, as well as allow us to evolve and experiment with various Budgie 11 components.
budgie-daemon: Centered around initial settings, power, and notification state handling. Effectively it will be feature parity with current Budgie Daemon and introduce a Budgie 10 compatibility layer for supported features.
budgie-desktop-shell: Centered around the various classes and foundation for supporting Budgie Panel, Budgie Menu and Raven.
Start development efforts on new Software Center implementation.
Continue development of new Software Center
Begin development of our next generation package manager, sol.
sold(sol daemon) as a Go JSON-RPC service that will call out to eopkg. This will be done until the rest of sol’s functionality is completed, for the purposes of enabling the Software Center to perform native package transactions.
Work on feature parity with eopkg, such as: