<div>so that means that aplha`s, beta`s en release candidates of KDE 4 will be in the next fedora rawhides? starting from now or FC8 development?</div>
<div>i would like this alot ^_^</div>
<div> </div>
<div>Thanx,</div>
<div>Mark.<br><br> </div>
<div><span class="gmail_quote">2007/5/3, Christopher Aillon <<a href="mailto:caillon@redhat.com">caillon@redhat.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Laurent Rineau wrote:<br>> On Thursday 03 May 2007 15:48:22 Kevin Kofler wrote:<br>>> Rex Dieter <rdieter <at>
<a href="http://math.unl.edu">math.unl.edu</a>> writes:<br>>> > When the hussle-bussle dies down (after F7 release?), we can work to<br>>> > submit these for review in Fedora proper.<br>>><br>>> Do we really want KDE 4 packaged like that in Fedora 8? May 24 + 6 months =
<br>>> November 24, that's a month after the planned KDE 4.0 release (October 23).<br>>> Thus I suggest upgrading all of KDE to the alphas in Rawhide as soon as<br>>> possible after Rawhide opens for F8
<br>><br>> Let wait and see if the KDE project can release KDE-4.0 in time.<br>><br>> I would not like F8 ship a release candidate of KDE4. The KDE desktop is the<br>> central part of the KDE spin of Fedora. It has to be stable.
<br><br>Release candidates are probably fine. We have shipped release<br>candidates of GNOME, and other software at times. Basically, RCs are<br>the releases that upstream thinks can be releases, but would rather get<br>
a wider amount of feedback before making it the actual release. In many<br>cases, upstreams simply rebuild the RC and call it final.<br><br>What we don't want are alphas or betas or random cvs snapshots in a<br>final release.
<br><br>--<br>fedora-devel-list mailing list<br><a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list">https://www.redhat.com/mailman/listinfo/fedora-devel-list
</a><br></blockquote></div><br>