From: George Shapovalov <georges@its.caltech.edu>
To: Gentoo Dev <gentoo-dev@gentoo.org>, gentoo-user@gentoo.org
Subject: [gentoo-dev] distributed ebuild processing
Date: Wed, 27 Mar 2002 19:45:50 -0800 [thread overview]
Message-ID: <200203280346.TAA05427@chamber.cco.caltech.edu> (raw)
Ok, gentoo mailserver seems to be up again, I'll try to post :-).
Here I want to propose an outline of a distributed ebuild processing system.
The system is supposed to allow for faster ebuild turnover by introducing
everybody interested into the process of ebuild review and testing while
keeping additional stress for core group low (may be even offloading some of
it off their shoulders). This same system will also allow for multiple
stability levels of resultant distribution (from very conservative to
"newest stuff included but watch out!") according to user choice.
Please see my detailed discussion on how this can be done in an efficient and
secure manner at:
http://www.its.caltech.edu/~georges/gentoo/epsp/proposal.html
This is a continuation of a previously initiated thread on gentoo-dev
"Unstable branch proposal - second round" (3-16), which in turn followed
after a week earlier thread "Proposal for an unstable branch" (3-03).
I do apologise for posting this message into two mailing lists. However I
feel that issues discussed here will be of interest for both communities.
Besides at this stage I am interested in receiving as much input as possible
from both developers and regular users.
I also have a question to core team. Should this proposal be entered into
bugzilla?
It did not make sense to do so in the early stages. Now as my view of the
matter somewhat stabilised and I got few replies along the same lines I was
thinking to wait for a few days (probably until 1.0 is released) evaluating
responses and tweaking the proposal and then to register this on
http://bugs.gentoo.org
George Shapovalov
reply other threads:[~2002-03-28 3:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200203280346.TAA05427@chamber.cco.caltech.edu \
--to=georges@its.caltech.edu \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@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