3 ms·

Same thing with Lennart's previous project PulseAudio which also has no real stable releases and basically relies on distros to try and take the beta-quality up

by makomk 11y ago

Same thing with Lennart's previous project PulseAudio which also has no real stable releases and basically relies on distros to try and take the beta-quality upstream releases and turn them into something that actually works reliably. (My favorite was the PulseAudio release that shipped with a change that was literally incomplete, changing the interal resampling API without changing all the resamplers affected. Crashing ensued. Was rolled back in the next release, but that came with a whole new set of feature patches with the same level of QA applied.) It probably doesn't help that they're both heavily developed by Red Hat, who see taking open source software and turning it into something stable and end-user viable as their secret sauce that justifies paying them lots of money.

cm3 11y ago
I've been able to avoid Pulseaudio and therefore didn't experience the issues it had in the past but I've heard that the new maintainers fixed stuff and are doing a better job, though I still don't use it and hence don't have first hand experience. I wouldn't blame Red Hat per se but the GNOME fall back they ship with RHEL is a joke and in no way resembles the old GNOME desktop Pixar was used to.
forgotpwtomain 11y ago
It's 2016 and I still have issues with pulseaudio, frankly I was somewhat surprised they let him replace init with systemd - given the terrible mess that pulseaudio has been historically.
- cm3 11y ago
  And audio professionals working on JACK don't seem to have any interest in pushing it while Lennart has been selling PulseAudio as the low-power alternative to JACK. Maybe he would have been a better fit within Android.
rwmj 11y ago
I agree with the rest of your post but I can assure you it's not the policy of Red Hat to release unstable upstream software. I am a Red Hat employee and I'm as annoyed as anyone that systemd doesn't have separate upstream development and stable releases. Also what's with the stupid versioning of systemd/udev? Having a single version number is simply a dumb idea.
- chris_wot 11y ago
  Now that is a real problem! I checked the git tags, and the major versions are indeed added over different time intervals... I had no idea there wasn't a time based release schedule. Do you know what the reason for that is?

by makomk 11y ago

cm3 11y ago

I've been able to avoid Pulseaudio and therefore didn't experience the issues it had in the past but I've heard that the new maintainers fixed stuff and are doing a better job, though I still don't use it and hence don't have first hand experience. I wouldn't blame Red Hat per se but the GNOME fall back they ship with RHEL is a joke and in no way resembles the old GNOME desktop Pixar was used to.

forgotpwtomain 11y ago

It's 2016 and I still have issues with pulseaudio, frankly I was somewhat surprised they let him replace init with systemd - given the terrible mess that pulseaudio has been historically.

cm3 11y ago
And audio professionals working on JACK don't seem to have any interest in pushing it while Lennart has been selling PulseAudio as the low-power alternative to JACK. Maybe he would have been a better fit within Android.

rwmj 11y ago

I agree with the rest of your post but I can assure you it's not the policy of Red Hat to release unstable upstream software. I am a Red Hat employee and I'm as annoyed as anyone that systemd doesn't have separate upstream development and stable releases. Also what's with the stupid versioning of systemd/udev? Having a single version number is simply a dumb idea.

chris_wot 11y ago
Now that is a real problem! I checked the git tags, and the major versions are indeed added over different time intervals... I had no idea there wasn't a time based release schedule. Do you know what the reason for that is?