Diff for /wikisrc/kyua/import.mdwn between versions 1.4 and 1.5

version 1.4, 2012/09/01 20:25:06 version 1.5, 2012/09/03 22:37:28
Line 2 Line 2
 [[!toc levels=2]]  [[!toc levels=2]]
   
 **Project owner: [Julio Merino](mailto:jmmv@NetBSD.org).**    **Project owner: [Julio Merino](mailto:jmmv@NetBSD.org).**  
 **Status: under review by tech-userlevel@ as of 2012-09-01.**  **Status: under review by tech-userlevel@ as of 2012-09-03.**
   
 The import of Kyua into NetBSD to replace the deprecated ATF tools is  The import of Kyua into NetBSD to replace the deprecated ATF tools is
 planned to happen in NetBSD 7.0.  The ATF libraries will remain in place,  planned to happen in NetBSD 7.0.  The ATF libraries will remain in place,
Line 138  that should be made before the plan can  Line 138  that should be made before the plan can 
 It is hard to tell how long this step will last, but possibly account for 2  It is hard to tell how long this step will last, but possibly account for 2
 to 4 weeks.  to 4 weeks.
   
   ## Address feedback as a new release
   
   Publish a new Kyua release that collects all the feedback from the reviews
   above.
   
   The list of issues to be addressed can be found by querying the
   [bug tracker](http://code.google.com/p/kyua/issues/list) for the
   [Milestone=Release0.6](http://code.google.com/p/kyua/issues/list?can=2&q=Milestone%3DRelease0.6&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles)
   keyword.  In particular, the following are the issues that have arisen from
   the review:
   
   * [Issue 40](http://code.google.com/p/kyua/issues/detail?id=40): Provide
     manpages instead of an info document.
   
 ## Import Kyua into src  ## Import Kyua into src
   
 As the [[introductory page to Kyua|/kyua]] describes, Kyua has been  As the [[introductory page to Kyua|/kyua]] describes, Kyua has been
Line 163  The specific steps to perform this impor Line 177  The specific steps to perform this impor
    binary in `/usr/bin`, a lot of test programs in `/usr/tests/kyua-cli`     binary in `/usr/bin`, a lot of test programs in `/usr/tests/kyua-cli`
    (around 100) and some auxiliary files in `/usr/share/kyua`.     (around 100) and some auxiliary files in `/usr/share/kyua`.
   
 1. Protect all products of Lutok and Kyua with the existing `MKATF` knob.  1. Protect all products of Lutok and Kyua with a new `MKKYUA` knob.  Once
    If desired, these could instead be protected by a new and separate     the ATF tools are removed, the existence of both the `MKATF` and
    `MKKYUA` knob, but because the transition is only temporary, I do not     `MKKYUA` knows will probably be confusing.  When that happens, we can
    think it's worth the effort.     revisit this decision by possibly replacing both with an `MKTESTS`.
   
 1. Update `bsd.test.mk` to generate `Kyuafile`s *in addition to*  1. Update `bsd.test.mk` to generate `Kyuafile`s *in addition to*
    `Atffile`s.     `Atffile`s.
Line 184  consider that some other tricky architec Line 198  consider that some other tricky architec
 The submission step to CVS, once all the code changes are ready locally,  The submission step to CVS, once all the code changes are ready locally,
 and any post-commit validation checks will take a few hours.  Any build  and any post-commit validation checks will take a few hours.  Any build
 breakage should be addressed in a timely manner (and can possibly be  breakage should be addressed in a timely manner (and can possibly be
 worked-around by setting `MKATF=no`).  worked-around by setting `MKKYUA=no`).
   
 ## Update documentation  ## Update documentation
   
Line 227  between different people in different ti Line 241  between different people in different ti
   
 At this stage, **at least one month shall be given to the community** to  At this stage, **at least one month shall be given to the community** to
 test the new tools and the new test results dashboards.  Collect feedback  test the new tools and the new test results dashboards.  Collect feedback
 and address requests as appropriate.  and address requests as appropriate (possibly by releasing and importing a
   new version of Kyua).
   
   One important thing to validate is that the results reported by `atf-run`
   and `kyua test` match with each other.  I have already been validating this
   with every public release of Kyua, but it has been a manual process.  To
   make this more reliable, I will set up a continuous testing machine of my
   own in which I will execute `atf-run` and `kyua test` in sequence (possibly
   within anita) and will add an automatic comparison of the exit status of
   each other.
   
 *Because the old `atf-run` and `atf-report` tools have not yet been dropped  *Because the old `atf-run` and `atf-report` tools have not yet been dropped
 at this point, we can spend as much time as necessary on this phase to get  at this point, we can spend as much time as necessary on this phase to get
Line 294  suite, and they were less detailed (most Line 317  suite, and they were less detailed (most
 tests) than the Kyua tests.  tests) than the Kyua tests.
   
 In order to mitigate this issue, the build of all pieces of Kyua will be  In order to mitigate this issue, the build of all pieces of Kyua will be
 protected by `MKATF` so that people allergic to C++ can avoid the whole  protected by `MKKYUA` so that people allergic to C++ can avoid the whole
 thing.  Even more, there are some other additional provisions described  thing.  Even more, there are some other additional provisions described
 below.  below.
   

Removed from v.1.4  
changed lines
  Added in v.1.5


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb