<br><br><div class="gmail_quote">On Thu, Oct 6, 2011 at 1:15 PM, Michael Schwendt <span dir="ltr"><<a href="mailto:mschwendt@gmail.com">mschwendt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Thu, 6 Oct 2011 12:55:53 -0400, S (solarflow99) wrote:<br>
<br>
> > 2011/10/6 solarflow99:<br>
<div class="im">> > > I noticed that packages that are built, don't go into the updates-testing<br>
> > > repo anymore? they'll still get put into updates right?<br>
> ><br>
> > I'm not sure to understand. packages built goes into<br>
> > rpmfusion-{,non}free-updates-testing for two weeks, then got pushed<br>
> > into stable if not problem occurs.<br>
> > The exeption is for our devel branch (still f16 at this time), until<br>
> > we branch f16.<br>
> > That step should be done in the middle of the month.<br>
> ><br>
><br>
><br>
> I don't see that. I just built for F-15 and EL5,6 but nothing goes into<br>
> updates-testing like it used to. Also EL-6 updates doesn't seem to be<br>
> browsable, just nonfree-testing.<br>
<br>
</div>Your memory doesn't serve you well. Fresh builds have _never_ entered<br>
updates-testing directly. They are placed in Plague's results repository<br>
(aka "needsign repo"). -> <a href="http://buildsys.rpmfusion.org/" target="_blank">http://buildsys.rpmfusion.org/</a><br>
>From time to time there are signed and pushed into the normal repos.<br>
<font color="#888888"></font><br></blockquote><div><br>oh:) thanks for clearing this up for me.<br> <br></div></div>