| 1 |
On 2/7/11 9:50 PM, Markos Chandras wrote: |
| 2 |
> My suggestion, as I said to fosdem, is to freeze, or take a |
| 3 |
> snapshot if you like, of the current tree, stabilize what you need to |
| 4 |
> stabilize, test the whole tree ( at least compile wise ) for a couple of |
| 5 |
> weeks and then replace the existing stable tree. Of course this requires |
| 6 |
> automated script testing, hardware facilities etc etc that we don't have |
| 7 |
> so claiming that stable tree is "stable" is quite wrong. |
| 8 |
|
| 9 |
This more thorough testing sounds really interesting. But do we really |
| 10 |
lack hardware resources? |
| 11 |
|
| 12 |
There are machines available for various arches at |
| 13 |
<http://www.gentoo.org/proj/en/infrastructure/dev-machines.xml>. I have |
| 14 |
at least a few chromium-related chroots on miranda, and I've never heard |
| 15 |
complaints, so it seems a few more chroots for arch testing wouldn't hurt. |
| 16 |
|
| 17 |
Of course for testing bootability and whether X11 starts up correctly, |
| 18 |
etc we'd probably have to host some virtual machines, but better compile |
| 19 |
testing (for example for toolchain updates) would be a good start. |
| 20 |
|
| 21 |
Paweł |
Archives