<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 25 February 2015 at 06:41, Stephen Gallagher <span dir="ltr"><<a href="mailto:sgallagh@redhat.com" target="_blank">sgallagh@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, 2015-02-23 at 17:03 +0200, Yanko Kaneti wrote:<br>
> On Mon, 2015-02-23 at 14:39 +0000, Petr Pisar wrote:<br>
> > On 2015-02-22, Yanko Kaneti <<a href="mailto:yaneti@declera.com">yaneti@declera.com</a>> wrote:<br>
> > > Introduce an "in-development" flag for packages in Fedora.<br>
> > ><br>
> > I like the confession that no in-developemnt code gets magically<br>
> > stable after<br>
> > half year of sitting in the Rawhide.<br>
><br>
> Indeed that was part of my thinking.<br>
><br>
> In-development packaging that might never reach maturity is a fact<br>
> of life and the idea was for us to embrace it and manage it in the<br>
> same place where we manage everything else.<br>
><br>
> Thanks for the feedback.<br>
<br>
</span>I'm somewhat of the opinion that code should never land in Rawhide<br>
that isn't stable upstream (or expected to be within that Fedora<br>
release cycle). Code that isn't ready and won't be ready in time<br>
belongs in a COPR.<br></blockquote><div><br></div><div>I have a couple of questions.</div><div><br></div><div>1) Does this change how most (or a sizable group of) developers see what rawhide is meant for?</div><div>2) To what extent does the COPR process need to be made more production ready and integrated into the build system to make those developers want to use it?</div><div><br></div><div>The COPR code is well done, but the resources it relies on are not. The cloud it runs on is a "this is something we work on when we have free 10 minutes" versus a "Saturday through Sunday 24/7/365" utility that we treat the main builders. As long as we aren't treating the COPR builders at that level, most developers are going to do builds on the main builders on the off chance that something is wrong or worse yet slooow. They will then just push to rawhide since it is an easy workflow.</div><div><br></div><div><br></div><div><br></div></div>-- <br><div class="gmail_signature"><div dir="ltr">Stephen J Smoogen.<br><br></div></div>
</div></div>