jablkoziemne<p><span class="h-card" translate="no"><a href="https://defcon.social/@ngn" class="u-url mention">@<span>ngn</span></a></span> Thanks for elaborating on this topic.</p><p>Im still not sure about <a href="https://101010.pl/tags/fedora" class="mention hashtag" rel="tag">#<span>fedora</span></a> being testing ground for <a href="https://101010.pl/tags/rhel" class="mention hashtag" rel="tag">#<span>rhel</span></a>, they surely have really formal way of introducing and documenting changes with their change proposals <a href="https://docs.fedoraproject.org/en-US/program_management/changes_guide/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">docs.fedoraproject.org/en-US/p</span><span class="invisible">rogram_management/changes_guide/</span></a> which to my knowledge from one of episodes of <a href="https://101010.pl/tags/techovertea" class="mention hashtag" rel="tag">#<span>techovertea</span></a> by <span class="h-card" translate="no"><a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention">@<span>BrodieOnLinux</span></a></span> are later reviewed by <a href="https://101010.pl/tags/rhel" class="mention hashtag" rel="tag">#<span>rhel</span></a> and merged/notmerged into it. Some people asked about <a href="https://101010.pl/tags/fedora" class="mention hashtag" rel="tag">#<span>fedora</span></a> and <a href="https://101010.pl/tags/rhel" class="mention hashtag" rel="tag">#<span>rhel</span></a> relationship in the past <a href="https://discussion.fedoraproject.org/t/request-for-a-detailed-breakdown-of-the-relationship-between-fedora-and-red-hat/86775" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">discussion.fedoraproject.org/t</span><span class="invisible">/request-for-a-detailed-breakdown-of-the-relationship-between-fedora-and-red-hat/86775</span></a></p><p>For the source code availability, even with <a href="https://101010.pl/tags/gpl" class="mention hashtag" rel="tag">#<span>gpl</span></a> <a href="https://101010.pl/tags/license" class="mention hashtag" rel="tag">#<span>license</span></a> you are only required to share the source code to the recipients of the application/whatever you are distributing/selling, just because most <a href="https://101010.pl/tags/gitforge" class="mention hashtag" rel="tag">#<span>gitforge</span></a> services allow everyone to view the projects stored on their servers, it doesn't mean it has to be like that - though, for open development process, maybe it should be? But that doesn't change that if <a href="https://101010.pl/tags/redhat" class="mention hashtag" rel="tag">#<span>redhat</span></a> called their <a href="https://101010.pl/tags/downstream" class="mention hashtag" rel="tag">#<span>downstream</span></a> <a href="https://101010.pl/tags/distro" class="mention hashtag" rel="tag">#<span>distro</span></a> "freeloaders", its really rude.</p><p>They are doing it for profit, I guess. Not caring about their potential customers will get them eventually. But besides that, everyone has to earn money somehow, and having <a href="https://101010.pl/tags/foss" class="mention hashtag" rel="tag">#<span>foss</span></a> product doesn't make it easy. </p><p>> best you can do is to put new tech and software into your repos, and encourage users to test and use it, which is what most rolling distros do</p><p>I disagree, although its good to have unstable features as opt-in, it introduces bias where the new features are only used by people that know about them, and know how to enable/switch to them. This way, you are severely reducing amount of useful bug reports that are crucial to know what are your users even doing.</p><p>Ideally you would perform AB tests, with ever increasing number of real users, and in case of issues you would simply <a href="https://101010.pl/tags/rollback" class="mention hashtag" rel="tag">#<span>rollback</span></a> the update to the latest stable version. Sadly, it would require that rollback feature, and prefill all system information in the bug report.</p>