Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 55488 invoked by uid 500); 17 Apr 2003 08:27:31 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 55475 invoked from network); 17 Apr 2003 08:27:30 -0000 Received: from main.gmane.org (80.91.224.249) by daedalus.apache.org with SMTP; 17 Apr 2003 08:27:30 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1964jQ-00010e-00 for ; Thu, 17 Apr 2003 10:26:56 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@avalon.apache.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1964jP-00010U-00 for ; Thu, 17 Apr 2003 10:26:55 +0200 From: Leo Simons Subject: Re: Excalibur Phase III List Date: Thu, 17 Apr 2003 10:27:38 +0200 Lines: 74 Message-ID: References: <3E9C37C5.9010000@apache.org> <3E9C4839.5020607@apache.org> <3E9D52F0.8000507@apache.org> <3E9D658B.1000202@apache.org> <3E9D8DD3.8010703@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en In-Reply-To: <3E9D8DD3.8010703@apache.org> Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Berin Loritsch wrote: Release List ------------ These will be released during phase III. > Compatibility (with Naming) > Fortress > Lifecycle seems like we have consensus on these three. > Store > XMLUtil we've had some requests not to move these back into cocoon (I have received another one privately). I don't really understand why, but it may have to do (speculation) with the perceived monolithic nature of the cocoon distribution, where people don't want the kitchen sink with a storage utility. My suspicion is that this nature is going / has gone away, with cocoon providing multiple smaller distributables. It also has to do with people who are planning to work on it here, but aren't atm. I am still not planning to work on them or even figure out how they work. I still think they should be moved back to cocoon, some other people do as well. If it is to remain here, I would really like the people with an interest in these packages to improve measurable stability prior to a release. My vote is a strong -0 on releasing them during phase III. "Expulsion" List ---------------- These won't be released during phase III and are looking for a new home. > Extension (what is the location?) IIUC, phoenix and merlin use this, Peter wants to move it into Spice, Steve wants to keep it where it is, and no-one else really cares for it. Hence it is still up for debate. IMO it is better for avalon (and phoenix, and merlin) if utility code like this is moved out. I have no problem with moving this to spice, and since that is what the primary author prefers, that sounds like the best idea. I don't want it released as part of excalibur as it is generic utility code which has nothing to do especially with avalon. > Loader (already removed grmbl) apparently Peter's proposal is loader --> spice-classman. Fine with that. +1 on grmbl. > ThreadContext (already removed grmbl) threadcontext --> just die? Fine with that. +1 on grmbl. > Policy (to Phoenix?) Sole maintainer for this is Pete, and IIUC he wants to move it into spice. Fine by me. We can also have it sit around in excalibur or sandbox cvs for "a month or so". "Alpha package" List -------------------- these go into avalon-sandbox. > XFC yep. cheers! - Leo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org