Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 86445 invoked from network); 9 Jan 2003 15:00:49 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 Jan 2003 15:00:49 -0000 Received: (qmail 4558 invoked by uid 97); 9 Jan 2003 15:02:05 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 4521 invoked by uid 97); 9 Jan 2003 15:02:05 -0000 Mailing-List: contact avalon-dev-help@jakarta.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 avalon-dev@jakarta.apache.org Received: (qmail 4508 invoked by uid 98); 9 Jan 2003 15:02:04 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Reply-To: From: "Berin Loritsch" To: Subject: [A5:Proposal] Where do we put stuff? Date: Thu, 9 Jan 2003 10:01:18 -0500 Message-ID: <000101c2b7ef$f7b50e60$f700a8c0@acsdom1.citius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I would like to unify where all current stuff for A5 proposals go in CVS. Some of it is code, but we have two places where we can place things. I Propose that we place all A5 stuff in avalon-scratchpad for the time being. The full location would be ${avalon-scratchpad}/avalon5 and would reflect how we might want to model the new Avalon project structure when we get our "avalon" CVS/SVN repository. It is important that we have a place for non-document ideas, which means it would definitely not be a match for the Wiki. It would also lighten the load on the jakarta-avalon CVS repository. I think we have some differing viewpoints on how and what should move ahead and when. In regards to Avalon 4.x, I think we are on board with Fortress release then Merlin release. As well as maintaining Phoenix in the time being. Any thoughts? -- To unsubscribe, e-mail: For additional commands, e-mail: