Since our Dev Tracker is finally online again many have already inquired about posting patches for the packages they maintain and/or want to update. Some who still had the build environment set up from before the outage have even already begun filling the tracker with their work.
This is much appreciated of course, but we also want to make clear that it'll take some time until we can review and push those package updates to the builder and repository.

Here is the progression of things that have to happen before we will be able to do so:

  1. Bringing our build server back online (we're currently waiting for DNS propagation) DONE!
  2. Testing an initial package build + repo update to verify the whole pipeline works correctly DONE!
  3. Coordinating with RIT to get our package repository properly mirrored again CHANGED TO CDN
  4. Pushing the first round of updates which includes security fixes, updates to the packaging tools, and a small number of important non-security fixes for common applications DONE!
  5. Short testing period for those updates DONE!
  6. First "real" sync DONE!
  7. Second round of important application and library updates DONE!
  8. Second sync DONE!

Until at least step 4 is complete you'll also not be able to set up the package build environment completely if you're a new contributor (or an old contributor who needs to set it up again), as there are updates for eopkg, arcanist and solbuild queued to handle changed URI schemes and the new phabricator version.

I suspect that after these steps we can start properly reviewing the first of your patches.

Importantly we're also planning to publish new ISOs sooner rather than later, so some package updates might be pushed to a point after those ISOs have been released (so the process of building and testing them can happen as early and fast as possible), depending on their importance.

After this first ISO refresh has been completed, which mainly serves to enable new hardware and spare users the huge initial update after installation, we can go full steam ahead on including all kinds of updates and improvements, big and small.

(Some details of this are still subject to change)

Thank you!

    Staudey stickied the discussion .

    Staudey we're also planning to publish new ISOs sooner rather than later,

    That's the best thing I've heard ... er, seen...for a long time. 688 updates needed after I installed my Solus Plasma VM a few days ago. Sure would be nice to cut that down a bit.

    I'd also like to ask whether these ISOs might contain a feature I've found very useful, during this time I've been relying on other distros. I've noticed that most recent installers offer three choices for setting up a disk: no swap, swap no hibernate, and swap + hibernate.

    Usinig gedit or equivalent to prepare the required partitions with the correct properties isn't exactly rocket science, but it is a PITA that should be easy for the installer to handle. That would potentially help a lot of users, especially those who intend to use the hibernate feature. (A great way to save electricity while you sleep, and unlike an ordinary shutdown, restores your workspaces automatically, so it's like you never left.)

        WetGeek I'd also like to ask whether these ISOs might contain a feature I've found very useful, during this time I've been relying on other distros. I've noticed that most recent installers offer three choices for setting up a disk: no swap, swap no hibernate, and swap + hibernate.

        The installer won't be touched yet for the first ISO release (which is mainly a package refresh, with better hardware support), but improvements in that area are definitely planned long-term (in fact there has been some talk about ways to improve the installation experience just today in the team channel).

            Staudey one of the best thing in Solus is how fast the system is installed so please, don't make any longer experience but even shorter or keep the same speed.
            I trust you guys other geek stuffs, just making ready for when you push every out for us to enjoy and get back on track

              Staudey To follow developments and test with a computer, it's always

              sudo eopkg add-repo Unstable https://mirrors.rit.edu/solus/packages/unstable/eopkg-index.xml.xz ?

                  atriaze Have you used the Unstable repository in the past? Because as Unstable user you have to expect instability at times, possibly series bugs, and follow our Solus Development room on Matrix for announcements about ongoing work to not accidentally break your system by updating at an inopportune time.

                      Staudey Indeed, I will install unstable Solus on my second computer and not on the work one.
                      I want to learn and go further, simply a personal approach.

                        Staudey unstickied the discussion .

                        ikey As long as it doesn't take too much of your time. It is pretty usable on mobile already, if maybe not 100% perfect.

                          ikey noticed it straight and switched to it already, making it better is always welcomed if it doesn't suck your time