List Archive: gentoo-releng
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Thilo Bangert wrote:
> Andrew Gaffney <firstname.lastname@example.org> said:
>> Thilo Bangert wrote:
>>> sign me up, though...
>> What exactly are you volunteering for? Like all the non-devs (4 of
>> them) who have offered help, I'm not going to find you a place in
> sounds reasonable. bug triaging, testing, building releases and such is
> what i had in mind. ultimately helping setup the automated builds...
I'm 90% done with setting up the automated builds. I've got a nice script I
At this point, I'm waiting for someone to get off their butt and fix bug #238685
so that I can complete a full build. On the arches that don't build on poseidon
(everything except x86/amd64), there will be a command in post_build() in their
respective .conf files that uses a specific SSH key to sync the build materials
to poseidon. They will then be automatically pulled to osprey (IIRC) for mirroring.
>> There are a few arches without release coordinators (or whose
>> coordinators are pulling double duty). Do you want to take over for x86
>> or one of the couple of arches that armin76 handles (sparc64 and ia64,
> release coordinator sounds a little too fancy for the kind of contribution
> i had in mind. but then again who know what the duties of that guy are?
Well, with the previous model, the arch coordinators were the suckers who did
the building and fixed bugs.
With our new model, the builds are mostly automated, so the coordinators will
just be the folk that occasionally poke the builds for their particular arch,
instead of babysitting them.
> where is work currently coordinated? it doesnt appear to be this mailing
> list ;)
The #gentoo-releng IRC channel and releng@ alias.
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Genkernel + Release Engineering Lead