Home About Blog Download Help Center Forum Get Involved
Logo
Home About Blog Download Help Center Forum Get Involved

Roadmap

The roadmap below is subject to change and not indicative of all the changes that may occur in the respective quarter.

Q1
Q1
Jan-Mar 2019

Budgie

January

  • Release Budgie 10.5

February

  • Release Budgie 10.5.1 with support for GNOME 3.30 Stack

March

  • Release Budgie 10.5.2 (if required) with support for GNOME 3.32 Stack

Cuppa

January

  • Tag a new release

Linux Hardware Qualifier

January

  • Tag a beta or stable release

Web Infrastructure

February

  • Deploy Flarum with OAuth Sign-In support with our Development Tracker. Flarum will replace our Forums and Google+ Community

March

  • Deploy re-designed Help Center with updated and restructured documentation

YPKG

February

Begin development of ypkg 3.

  • Consolidate and enforce consistency in our package tooling
  • Introduce desired functionality such as:
    • SPDX compliance checking
    • Validation of package names, release numbers, and version numbers
    • Checking of mandatory and empty keys

March

Continue development of ypkg 3.

  • Implement various ypkg 3 build processes
  • Incorporate eopkg-deps and ypkg-update-checker like functionality
Q2
Q2
Apr-Jun 2019

Budgie

April

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.

  • Focused on starting development of the following 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.

May

TBD

June

TBD

Software Center

April

Start development efforts on new Software Center implementation.

  • Written in C and GTK3 with proper desktop handling on Plasma (not use GTK Headerbar)
  • Introduce support for Flatpak and Snaps via our planned plugin architecture
  • Introduce a new user experience

May

Continue development of new Software Center

June

  • Tag first stable release of new Software Center

Sol

April

Begin development of our next generation package manager, sol.

  • Release 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.
  • Additionally introduce a Third Party backend to facilitate installation of Third Party repo items using ypkg, which would not otherwise be supported by Flatpak or Snaps (such as Google Chrome).

May

Work on feature parity with eopkg, such as:

  • Package Management
  • Repository Management
  • Searching

June

  • Tag first stable release of sol

Web Infrastructure

April

  • Start work on replacing blog with a new Activity Hub to consolidate all relevant Solus activity from the team (blogs, social media posts, development tracker activity) in a single place.

May

  • Start work on various tooling for social media cross-posting, which will be able to be leveraged by the Team to post across:
    • Activity Hub
    • Facebook
    • Flarum
    • Mastodon
    • Reddit
    • Twitter

June

  • Deployment of new Activity Hub

ypkg

April

  • Tag first stable release of ypkg 3
Q3
Q3
Jul-Sept 2019

Budgie

  • Budgie 11 development across entire quarter.
  • Aim for public alpha builds on top of a Solus ISO around August
    • Formal development to transition to GitHub as well

Sol

  • Sol development across entire quarter.
  • Planned release of sol 1.5, with some items such as (but not limited to):
    • A new binary index format
    • A new metadata + files format
    • Enforced index signing

usysconf

  • Rewrite at some point in Q3 to be entirely configuration-based, eliminating the requirement to learn and write C just for new usysconf handlers
Q4
Q4
Oct-Dec 2019

Budgie

  • Budgie 11 development across entire quarter
  • Aim for public beta builds on top of a Solus ISO around October

Sol

  • Sol development across entire quarter.
  • Planned release of sol 2.0, with items such as (but not limited to):
    • The conversion of sol daemon to C
    • Improved deltas
    • Improved index and package repair functionality