<br><br><div class="gmail_quote">On Thu, Apr 1, 2010 at 5:54 PM, Sam Sharpe <span dir="ltr"><<a href="mailto:lists.redhat@samsharpe.net">lists.redhat@samsharpe.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 1 April 2010 22:23, Marcel Rieux <<a href="mailto:m.z.rieux@gmail.com">m.z.rieux@gmail.com</a>> wrote:<br>
> On Thu, Apr 1, 2010 at 5:06 PM, Chris Adams <<a href="mailto:cmadams@hiwaay.net">cmadams@hiwaay.net</a>> wrote:<br>
>><br>
>> Once upon a time, Sam Sharpe <<a href="mailto:lists.redhat@samsharpe.net">lists.redhat@samsharpe.net</a>> said:<br>
>> > You keep saying this. I shall make only two points as I am bored of<br>
>> > saying this time and time again.<br>
>><br>
>> I would welcome you stopping saying this, since you present two extremes<br>
>> as the only possible choices (which they are not).<br>
><br>
> Though I've been providing this link time and again, Mr Sharpe has chosen to<br>
> ignore it:<br>
><br>
> <a href="https://fedoraproject.org/wiki/Stable_release_updates_vision" target="_blank">https://fedoraproject.org/wiki/Stable_release_updates_vision</a><br>
<br>
</div>Actually I read it before, although I have no idea whether it was due<br>
to a post by you - I believe it to be largely a statement of the<br>
current status-quo. Perhaps you read it differently to me.<br>
<br>
* The update repositories for stable releases of the Fedora<br>
distribution should provide our users with a consistent and high<br>
quality stream of updates.<br>
<br>
I haven't seen huge issues with updates for releases. I realise<br>
other people might have, but that doesn't indicate an endemic problem<br>
of brokenness in Fedora, nor that the aims have changed.<br>
<br>
* Stable releases should provide a consistent user experience<br>
throughout the lifecycle, and only fix bugs and security issues.<br>
<br>
Again, I haven't personally seen evidence that Updates to a Fedora<br>
release have massively changed the User Experience - but then I'm not<br>
a KDE user.<br>
<br>
* Stable releases should not be used for tracking upstream version<br>
closely when this is likely to change the user experience beyond<br>
fixing bugs and security issues.<br>
<br>
This is currently true - they do not.<br>
<br>
* Close tracking of upstream should be done in the Rawhide repo<br>
wherever possible, and we should strive to move our patches upstream.<br>
<br>
This is the current situation<br>
<br>
* More skilled and/or intrepid users are encouraged to use Rawhide<br>
along with participating in testing of stable branches during the<br>
development and pre-release period.<br>
<br>
This is the current situation<br>
<br>
* Stable releases, pre-release branches, and Rawhide have a graduated<br>
approach to what types of updates are expected. For example, a<br>
pre-release branch should accept some updates which a stable release<br>
would not, and rawhide would accept updates that are not appropriate<br>
for either a stable release or a pre-release.<br>
<br>
This is the current situation. e.g. major software versions can<br>
change between F12 Alpha and Beta releases.<br>
<br>
* Project members should be able to transparently measure or monitor a<br>
new updates process to objectively measure its effectiveness, and<br>
determine whether the updates process is achieving the aforementioned<br>
vision statements.<br>
<br>
Not something I can comment on.<br>
<br>
As I understand it, in the above terminology:<br>
<br>
Rawhide == Rawhide<br>
Pre-release == Fxx Alpha, Fxx, Beta, Fxx RC<br>
Stable == Fxx<br>
<br></blockquote><div><br>So! No more 'The "Stable" offering is Red Hat Enterprise Linux.' ?<br><br>What? OK, RHEL might finally prove more solid than Fedora, but final is stable. Only security patches and important bug fixes should be uploaded. No program updates. I'm glad to learn we agreed all along!<br>
<br>Which means that, for instance, developers should think twice before quitting the KDE 3.5.x branch and going for 4.0. Since testing means "going soon to the final, stable release", KDE 4 remains in rawhide, even though it evolves to new dot versions, until it's deemed stable enough for the next final release. That's the way Patrick Volkerding does it for Slackware.<br>
<br>For non-developers using Final , "release early. release often" is "released too early, released too often."<br><br>Of course, nothing prevents Red Hat's own geeks, or anybody feeling adventurous, from enabling the Rawhide repository.<br>
<br>So, everybody is kept happy.<br><br><br></div></div>