| 1 |
On Fri, Jul 26, 2013 at 4:24 AM, Matt Turner <mattst88@g.o> wrote: |
| 2 |
|
| 3 |
> Can we make autobuilds go to /experimental and then only move them to |
| 4 |
> /releases when someone actually tests them? |
| 5 |
> |
| 6 |
> |
| 7 |
Even though this sounds good and makes sense, if we don't even have enough |
| 8 |
people to work on things now, this would only make things worse (imho). |
| 9 |
|
| 10 |
|
| 11 |
> Looking at bugzilla and listening in #gentoo-releng, it's kind of |
| 12 |
> embarrassing how often someone downloads a Live CD only to find out |
| 13 |
> that networking is totally broken by a udev upgrade, or something to |
| 14 |
> that effect. |
| 15 |
> |
| 16 |
> |
| 17 |
There's no way to deal with this breaks when those committing them don't |
| 18 |
even warn us about them. |
| 19 |
|
| 20 |
|
| 21 |
> We don't commit version bumps straight to stable; I don't see why we |
| 22 |
> do with release media. |
| 23 |
> |
| 24 |
> Matt |
| 25 |
> |
| 26 |
> |
| 27 |
The alternative here is the automated testing that I've talked about with |
| 28 |
others on FOSDEM and Prague last year, but that still needs to be done. |
| 29 |
Amongst other testing, the idea would be to pick the latest ISO and boot it |
| 30 |
on some virtualization platform and catch the console output to ensure it |
| 31 |
booted successfully and not tests failed. |
| 32 |
|
| 33 |
Regards, |
| 34 |
|
| 35 |
Jorge |
Archives