On Fri, Dec 7, 2012 at 8:55 PM, "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote: > Hey people, what are we going to do with bugs like: > > <https://bugs.gentoo.org/show_bug.cgi?id=421839> > <https://bugs.gentoo.org/show_bug.cgi?id=445848> > > I'd like to help with things. Is the process of building livecd .isos > and stages documented somewhere? I'd like to reproduce problems locally, > work on fixes, and join the release teams. > > I also think points made at > <https://bugs.gentoo.org/show_bug.cgi?id=438234> are very reasonable, > and we should do more testing of published media/stages. > > The serious problem here is that we need *new* users. A non-working > install CD is a really bad thing here, don't you think? ;-) > > Again, I'm willing to do the work, just need some documentation/pointers. > > Paweł >
Indeed, it is a problem. Fortunately the missing /run was confirmed fixed earlier today on IRC, so that should be resolved shortly and with it the second bug you mention. The main problem here is that it's really easy to break the release media. Mistakes happen and are a normal part of development, but for instance stabilizing linux-headers-3.6 (bug 443532) with multiple outstanding bugs caused some completely predictable breakage. I have never once been able to grab a portage snapshot and build a stage 1, 2, 3 series from it without encountering at least a couple of problems with the tree. I think we should consider things that break release media serious regressions. I don't know what that entails specifically, but whether it need be QA bashing down your door or a quick fix or revert, it sure would be nice to get Gentoo to a place where release media always works. In any case, we'd love some extra help. jmbsvicetto and armin76 have been managing all of the autobuilds, to my knowledge, for a long time. catalyst could also use some work. Spend a day or so building some stages and I have no doubt you'd find things you want to change. :) In short, I think the conversation we should be having should be about how to avoid breaking release builds and how to quickly fix problems when they're discovered. Thanks, Matt
