hi George, We need to determine what level of test coverage needs to be rolled out and when. For the moment much of the test coverage is in the platform space -- we probably want to roll out the application checker tools at the same time.
For the core platform tests, we will need to decide how to handle the differences between the POSIX and UNIX standard semantics, which of those should be waivered in some way for LSB certification(either withdrawn from the default scenario or a version of the test forked under the LSB.os tree or just expected to fail). Once we have defined the set of tests we will need to cut a binary version of the tests using the lsbdev package to deploy for formal certification. There is someway to go initially , we need to define the coverage, for example if FHS 2.2 is ever completed do we want to include test coverage for that , at the moment we have coverage for FHS2.1. Another example is the LSB-OS testset where we are in beta, with over 100 exceptions that need considering. Is that a testset we want to deploy in the initial rollout? What about Commands ? regards Andrew On Apr 11, 2:31pm in "test suite", [EMAIL PROTECTED] wrote: > During the LSB meeting today we discussed the completion of LSB v1.0 and > the convergence of the testsets. What will the criteria be for syncing, > freezing, then version numbering for LSB v1.0? > > Task 27920: convergence plan for spec and tests > > https://sourceforge.net/pm/task.php?func=detailtask&project_task_id=27920&group_id=1107&group_project_id=3050 > > Task 27941: lsb certification program > > https://sourceforge.net/pm/task.php?func=detailtask&project_task_id=27941&group_id=1107&group_project_id=3050 > > > George Kraft IV > [EMAIL PROTECTED] > IBM Linux Technology Center > FSG's Linux Standard Base > >-- End of excerpt from [EMAIL PROTECTED]
