From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DATE_IN_PAST_12_24, INVALID_DATE,MAILING_LIST_MULTI,NO_RELAYS autolearn=no autolearn_force=no version=4.0.0 Received: from drobbins by cvs.gentoo.org with local (Exim 3.30 #1) id 15RJgJ-0003Cs-00 for gentoo-dev@cvs.gentoo.org; Mon, 30 Jul 2001 14:30:27 -0600 From: Daniel Robbins To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] Organizing user ebuild submissions Message-ID: <20010730143027.S14345@cvs.gentoo.org> References: <0107302259100D.00612@localhost> <20010730140038.R14345@cvs.gentoo.org> <0107302307330H.00612@localhost> <87d76i9n9q.fsf@codefactory.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <87d76i9n9q.fsf@codefactory.se>; from hallski@gentoo.org on Mon, Jul 30, 2001 at 10:26:25PM +0200 Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Mon Jul 30 14:31:02 2001 X-Original-Date: Mon, 30 Jul 2001 14:30:27 -0600 X-Archives-Salt: 5039479f-c4e3-4ffb-9e94-79228e5e7e79 X-Archives-Hash: f2cd2dfbed555e3636a72158f983e533 On Mon, Jul 30, 2001 at 10:26:25PM +0200, Mikael Hallendal wrote: > Dan Armak writes: > > > I wouldn't mind handling the mailing-list side of the story - grabbing > > all ebuilds and putting them wherever and informing whoever. But many > > ebuilds come through for packages I don't use and in many cases can't > > test. I don't think any one developer could or should handle the > > testing, that's why we have teams. We can have an "incoming" ebuild > > tree (in cvs or elsewhere) and developers could grab ebuilds that fall > > under their area of interest, test them and put them either in the > > stable or unstable cvs trees. > > I also think this is the way of doing it. Perhaps, when you find an > ebuild in the mailinglist you can commit it to some place in cvs and > add a wiki todo about it giving it to the correct team. This way it > will be easy to track what "your" team has to test. Good idea. Dan, go ahead and create and add a /usr/portage/incoming directory to CVS and check all new ebuilds in there. Then, post a wiki item for each new ebuild (or batch of related ebuilds) and assign the wiki item to the appropriate team, priority "low". Thanks for doing this. Best Regards, -- Daniel Robbins Chief Architect/President http://www.gentoo.org Gentoo Technologies, Inc.