1 |
On Mon, Jul 29, 2013 at 12:05 PM, Jorge Manuel B. S. Vicetto |
2 |
<jmbsvicetto@g.o> wrote: |
3 |
> |
4 |
> On Fri, Jul 26, 2013 at 4:24 AM, Matt Turner <mattst88@g.o> wrote: |
5 |
>> |
6 |
>> Can we make autobuilds go to /experimental and then only move them to |
7 |
>> /releases when someone actually tests them? |
8 |
>> |
9 |
> |
10 |
> Even though this sounds good and makes sense, if we don't even have enough |
11 |
> people to work on things now, this would only make things worse (imho). |
12 |
|
13 |
Everyone that's expressed concerns about this plan seems to do so |
14 |
based on the idea that we must move things to /releases very often. I |
15 |
do not believe this to be the case. |
16 |
|
17 |
Release media doesn't need to be the latest and greatest, it just |
18 |
needs to be able to install Gentoo. |
19 |
|
20 |
The stages aren't so much a problem, since you're already able to |
21 |
configure and install software when using them, but the LiveCDs should |
22 |
be stable and tested. |
23 |
|
24 |
I specifically care that the LiveCDs are tested before being moved to |
25 |
/releases. I think it's perfectly okay to leave stages in |
26 |
/experimental. |
27 |
|
28 |
>> Looking at bugzilla and listening in #gentoo-releng, it's kind of |
29 |
>> embarrassing how often someone downloads a Live CD only to find out |
30 |
>> that networking is totally broken by a udev upgrade, or something to |
31 |
>> that effect. |
32 |
>> |
33 |
> |
34 |
> There's no way to deal with this breaks when those committing them don't |
35 |
> even warn us about them. |
36 |
|
37 |
I think this is a separate problem and should be treated as such. We |
38 |
certainly can't claim "oh, someone pushed a commit the broken udev, so |
39 |
it's not our fault that the release media is broken." Whose fault it |
40 |
is is immaterial to the user who just downloaded something they expect |
41 |
to work from /releases and is now unable to install Gentoo. |
42 |
|
43 |
We can work on that problem, but I don't think it's going to go away |
44 |
easily. We could avoid almost all of the problems if we simply tell |
45 |
users which LiveCD images are known to work. |
46 |
|
47 |
> The alternative here is the automated testing that I've talked about with |
48 |
> others on FOSDEM and Prague last year, but that still needs to be done. |
49 |
> Amongst other testing, the idea would be to pick the latest ISO and boot it |
50 |
> on some virtualization platform and catch the console output to ensure it |
51 |
> booted successfully and not tests failed. |
52 |
|
53 |
Some recent problems have involved linux-firmware being broken. I |
54 |
don't think virtualization will help notice that, e.g., the Tigon 3 |
55 |
firmware is missing. |