On Mon, 2010-01-04 at 10:24 +1000, Noriko Mizumoto wrote:
>> I am Noriko Mizumoto, coming from Fedora Localization
>> As we are in scheduling period, I'd like to propose new QA test to be
>> created. Here is the detail.
> Hi :)
> I think we'd be happy to help with this however we can, but it seems
> like something that obviously depends on linguistic ability! We can
> contribute any of us in QA who speak languages other than English,
Great, thank you!
So, anyone on the list who is proficient in a language other than
English - please do help out Noriko :)
> For building images to test - in fact, live images are generated
> automatically, nightly, available at:
> would this be to your requirements?
OH, this sounds awesome :-)
Let me just double check, this image does contain all latest Fedora 13
packages built at that time, right? 
Yes, that's what it's intended for.
I am a bit of afraid if nightly build overrides next night build.
F13, in this case, I like to have "nightly-composes of 5-Mar-2010" image
available between 5th and 16th of March. This allows translators to have
QA test with exact one same image and file a bug if needed.
We don't typically do this, but I'm sure we could make arrangements to
keep an image available for a given time. I think we wind up having a
fairly-recent image available for one reason or another through most of
the process anyway; I'll CC Jesse, who can explain in more detail.
There's usually a recent snapshot or test compose or pre-release or
_something_ available at any given point, right Jesse?
When we file a bug, Version-Release should be "nightly-composes
5-Mar-2009". Is this sufficient for the packager to look in and fix if
needed? e.g. 
Well, this isn't an option. You just set the release to Rawhide. You can
mention the nightly image date and the specific package version in the
bug report if you like. Generally packagers will ask if they need
Does this image also contain python-nss? This is to perform liveinst.
This I don't know off the top of my head. You could download the latest
nightly and test. If it's not, we can look at fixing that. Frankly the
closing of the bug report seems a little odd to me; if anaconda needs
python-nss to run, it should depend on it, I would think. We shouldn't
have to add it to the live image manually. Unless there's some specific
reason not to put it in the dependencies.
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org