Danny Backx wrote: > Pedro, > > How do you feel about keeping track of what we know and have tested with > a file such as the attachment ? >
I think keeping status reports is good. We need to be objective and reproducible on this. Most of the tools we use have testsuites (binutils, gcc, gdb), and we should use those to help keep track of status. > We could store it in svn in the docs directory. Can we write this kinds on docs in tex or something else that *outputs* html? Having to muck up on html directly is such a horrid thing to do. > > Overview > > The goal of this file is twofold : > > * to outline a test plan > * to keep track of what's been verified for some release > In practice, we'd need to automate the testing somehow, and write a 'release steps' doc. But I'm not objecting to your current form, though. Be my guest to upload something and work from there. Been bitten already by the 'upload only when ready' mentality often enough :-) -- Pedro Alves ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
