@devrtz so true. (as a newbie) I wonder if there are nightly builds people (not maintainers) can opt into to get these 'new features' and WIPs?
Or would that be too much of a hassle for developers of core components?
At least for the distributions I'm involved in there are no (automatic) "nightly" builds (of unreleased upstream software).
If a project builds distro packages in their CI, you can of course grab and install those. But you have to go hunting for it.
Flatpak developers sometimes/often(?) ship nightly, f.e. org.gnome.Calendar.Devel
so if you use flatpak this might be an option and should still be relatively safe (in terms of breakage).
@devrtz yeah I've seen a few nightly flatpaks. So if people want the latest they should follow the steps to build the development version to test and they are fully in control of the process, not some community packager.
In #debian (and #pureos) packages are uploaded to the unstable (or landing) suite and usually migrate after a few days to testing (or byzantium) suites unless migration is blocked due to some breaking bug.
You could enable those suites in your /etc/apt/sources if you want to get updates a few days before the "general public". But you also might end up getting some bugs earlier as well, so it's double-edged sword.
- Start hacking on Feature/Bug X
- Open (WIP/Draft) MR
- Hack some more
- Once it's ready for review unWIP/undraft it
- Fix issues that crop up during review until everyone is happy
- Test drive it for a bit
- Repeat for Feature/Bug Y
- Make release
- Update the package and upload it
But distros should warn their users what they are in for when selecting their distro. So that users make an informed choice.
A distro shipping unfinished WIP work in core packages without warning users is reckless to say the least.
A newer server operated by the Mastodon gGmbH non-profit