In the not so distant past, Solus followed a static point release model. Our most current release at this time is 1.2, with a 1.2.1 planned to drop in the near future. However, we also recently announced our move to a rolling release model. As such, these two schools of thought are in contradiction of one another.
Going forward, the old release schedule is officially, entirely dropped, and the branching pattern of a point-release-system is also shed.
#### Important Points
#### 1.2.1 – Update
We can only apologise in announcing that yes, 1.2.1 has been delayed. This has primarily come about due to a mixture of circumstances (work schedules), a wish to ensure consistency and longevity in the installations (GNOME 3.20 updates), and the migration to a rolling release model. As soon as it is appropriate, 1.2.1 will be released. However, the release schedule is now officially withdrawn, leaving us some extra time to get 1.2.1 polished to the level we require.
#### Coming Items
Our upcoming update list involves, but is not limited to: - Update to GCC 6.1.0 (ongoing right now, handling libmpx incorporation) - Move to GNOME 3.20.x - Update to X.Org Server 1.18.4 - Ongoing rebuilds to utilise newly available CPU features on the build server to improve Solus packages - Budgie 10.2.7 – whilst we initially envisaged going directly to 10.3, which has outstanding goals, we’ve opted to provide a maintenance release of Budgie to accommodate all Budgie downstreams in the near future, due to the already extensive diff since 10.2.6. You can see the latest git build in the featured image for this post.
The core advantage to the withdrawal of this static release schedule is that it in fact enables us to land features with a higher velocity, and maintain that velocity over time. With the move to a rolling release, one of our primary goals is in increasing the project cadence. As such, this frees us up to land future updates and refreshed ISOs, as and when new features, fixes and changes are available, as opposed to being tied to a rigid schedule. In the long run, this will result in more ISO releases and updates, enabling incremental testing of technology in Solus.