> * Developers to experiment with and present new concepts for the CDs
> * Maintainers to help build the CDs, correct flaws in the build
> scripts, update (and test) existing software included on the CDs
> * Testers to download the isos, run as much of the software on as wide
> a range of machines as they can, and report. Yes, please report both
> successes and failures
> * Editors to help write and maintain documentation for various aspects
> of the CDs
Hello Jeremy,
I would love to help. I do have a couple of questions so we can
hopefully be more effective at this.
1. What are some examples of common issues that users have reported
that you feel would benefit from a bit of automated testing? There
will always be a need for ad-hoc, but automation can help with some of
the more trivial sanity checks.
2. I could work on scripts that do some basic sanity checks at
runtime, but if that's already in place I could focus on some more
feature-specific problem areas.
3. Is it safe to assume that the results of testing the binaries and
other files included in the "minimal" version should also apply to the
X version? In other words, are the X+XFCE additions simply appended,
or are modifications of the "minimal" cd required to build the X cd?
This way, tests on the binaries in the "minimal" cd won't have to be
run against the X cd since they have already been done in the
"minimal" cd. (I hope I'm not too confusing here)
4. If it is decided that the LiveCD will have a package manager, how
much can this be relied on when dropping in different versions of
{libraries,binaries}?
In the meantime, I guess I will get the latest dev release and poke
around a bit more than I have in the past to get some ideas.
Thanks!
Craig Jackson
(TheEpitome)
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
