On Thu Jun 21, 2001 at 02:52:16PM +0100, Michael Brown wrote:
> > > > > How many more times should I report this bug? :-(
> > > > Exactly when did you report the bug? Is it possible the packages were
> > > > built prior to your reporting the bug? Did you check the cooker
> > > > packages?
> > > > rpm -qip the kdelibs packages and see if it was built after you
> > > > reported it.
> > > Reported Jun 10, at which time 2.1.2-3mdk was not available on any of the
> > > mirrors that I check (both rpmfind and proxad.net). The problem therefore
> > > seems to be in the mirroring: both rpmfind and proxad are (AFAIR) primary
> > > mirrors and so I usually treat them as being definitive; if a package is
> > > not present then I assume it doesn't exist.
> > QA process is not a 24hr deal... =) It sometimes takes a little bit
> > longer, and kdelibs is a big package that needs thorough testing
> > (this isn't cooker we're talking about!). So the delay is not in
> > mirroring, but in QA. We could do it faster and not as thorough, but
> > then we'd be doing it over again many more times, I'm sure.
>
> OK, that makes sense, but how about releasing the packages to cooker as
> soon as they are built and then releasing as updates once QA is complete?
> That way, everyone knows when an update is being worked on and you also
> benefit from extra testing.
I just checked, and kdelibs in cooker is 2.2-0.alpha2... I don't know
how we can get kdelibs 2.1.2 into cooker without causing even more
problems... =) Remember, cooker moves fast and usually has the latest
and greatest... versions that we support in updates cannot always use
cooker as a vehicle for testing.
--
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
- Danen Consulting Services www.danen.net, www.freezer-burn.org
- MandrakeSoft, Inc. Security www.linux-mandrake.com
Current Linux kernel 2.4.3-20mdk-win4lin uptime: 9 hours 18 minutes.
PGP signature
