Archives
Archives
| From: | Michael Orlitzky <mjo@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] The changes about the stabilization process | ||
| Date: | Mon, 26 Dec 2016 00:30:22 | ||
| Message-Id: | 939ef52d-878f-677d-73cf-9c0ef02aa9cb@gentoo.org | ||
| In Reply to: | Re: [gentoo-dev] The changes about the stabilization process by Andrew Savchenko |
||
| 1 | On 12/25/2016 02:55 PM, Andrew Savchenko wrote: |
| 2 | > |
| 3 | > What is a recommended way to describe how runtime testing should be |
| 4 | > done? Some packages are quite complex and it is desired not only to |
| 5 | > run them, but to run with some args or do some actions. |
| 6 | > |
| 7 | > Some ideas: |
| 8 | > |
| 9 | > ... |
| 10 | |
| 11 | The Emacs team came up with this |
| 12 | |
| 13 | https://wiki.gentoo.org/wiki/Project:Emacs/Test_plans |
| 14 | |
| 15 | and I tried to copy it, mostly for my own reference: |
| 16 | |
| 17 | https://wiki.gentoo.org/wiki/Project:Haskell/Test_plans |
| 18 | |
| 19 | We could easily extend that idea to individual packages. |