From: Andrew Gaffney <agaffney@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Call for feature requests for 2008.0
Date: Thu, 24 Jan 2008 13:37:43 -0600 [thread overview]
Message-ID: <4798E907.5000408@gentoo.org> (raw)
In-Reply-To: <c0526ddf0801241131t4f4822a1r30dc2eb511f0945e@mail.gmail.com>
Michael Marineau wrote:
> On Jan 24, 2008 10:23 AM, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
>> Hello everyone,
>>
>> Release Engineering is in the planning stages for 2008.0, so we're
>> asking for input from the community on things that they'd like to see
>> added/changed/removed from our release media. All requests should be
>> something Release Engineering actually can accomplish, like profile
>> changes, or changes to the stages or ISO images. We are interested in
>> all ideas, though we may only choose a few, as time and mirror space are
>> definite considerations.
>>
>> So, if you'd like to see something changed in Gentoo's releases, come on
>> over to the gentoo-releng mailing list and join in the fun!
>
> I've got one tiny request and a slightly unrelated question. First,
> could we add rsync to the minimal install cd images? I tend to find
> myself booting to a cd and then copying over an rsync binary.
No. See bug #90414 for details.
> Second, I saw on the release meeting agenda there was an item about
> doing automated internal builds. I missed the meeting and I haven't
> seen anyone post a log yet so I don't know what was discussed. I
> currently do automated weekly stage{1,2,3} builds for use at the OSL
> for x86/amd64 and could easily add ppc64. Would people find it useful
> if I started posting those publicly in some semi-official manner?
These builds aren't for public consumption. They're for QA purposes. We've
already been doing automated weekly stage[1-3] builds for x86/amd64 on poseidon,
and I think another arch may have been using my script, as well.
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
--
gentoo-releng@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-24 19:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 18:23 [gentoo-releng] Call for feature requests for 2008.0 Chris Gianelloni
2008-01-24 19:31 ` [gentoo-releng] Re: [gentoo-dev-announce] " Michael Marineau
2008-01-24 19:37 ` Andrew Gaffney [this message]
2008-01-25 3:11 ` [gentoo-releng] " M. Edward (Ed) Borasky
2008-01-25 4:25 ` Andrew Gaffney
2008-01-25 14:46 ` M. Edward (Ed) Borasky
2008-01-25 17:23 ` Chris Gianelloni
2008-02-04 21:20 ` [gentoo-releng] Call for feature requests for 2008.0 - Universal-CD Peter Weber
2008-02-04 21:22 ` Chris Gianelloni
2008-02-04 21:25 ` Randall D. Wald
2008-02-04 21:28 ` Andrew Gaffney
2008-02-04 21:47 ` Peter Weber
2008-02-04 21:49 ` Markus Hauschild
2008-02-04 21:58 ` Andrew Gaffney
2008-02-04 22:03 ` Markus Hauschild
2008-02-04 22:04 ` Peter Weber
2008-02-04 22:05 ` Dale
2008-02-04 22:23 ` Peter Weber
2008-02-05 20:10 ` Jorge Manuel B. S. Vicetto
2008-02-05 21:55 ` Dale
2008-02-04 22:03 ` Peter Weber
2008-02-04 22:36 ` Chris Gianelloni
2008-02-04 22:39 ` Markus Hauschild
2008-02-04 22:35 ` Chris Gianelloni
2008-02-04 22:50 ` Peter Weber
2008-02-04 23:30 ` Chris Gianelloni
2008-02-04 21:26 ` Andrew Gaffney
2008-02-04 21:33 ` Markus Hauschild
2008-02-04 22:30 ` Chris Gianelloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4798E907.5000408@gentoo.org \
--to=agaffney@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox