Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 45602 invoked from network); 7 Dec 2001 14:15:46 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Dec 2001 14:15:46 -0000 Received: (qmail 16788 invoked by uid 97); 7 Dec 2001 14:15:46 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 16758 invoked by uid 97); 7 Dec 2001 14:15:45 -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 16747 invoked from network); 7 Dec 2001 14:15:45 -0000 Message-ID: <3C10CF7B.2060900@apache.org> Date: Fri, 07 Dec 2001 09:17:31 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120 X-Accept-Language: en-us MIME-Version: 1.0 To: Avalon Developers List Subject: [Code Freeze] Avalon should be in code freeze (was Re: *Temporarily* relenting and moving on.) References: <3C0F7AEB.1010905@apache.org> <200112062236.fB6ManO03335@mail016.syd.optusnet.com.au> <3C1036EC.1000002@apache.org> <200112070506.fB756PO23291@mail016.syd.optusnet.com.au> <3C10CE70.6020202@apache.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 realized my last post should have had a new title so as not to be lost. Please come up with issues for Avalon Framework--and we will decide if it is a showstopper, a minor but allowable change (spelling/correction of documentation), or something that will be placed on hold. The CVS should have 100% back compatible code. If this is not the case, please alert me ASAP. Berin Loritsch wrote: > Peter Donald wrote: > >> On Fri, 7 Dec 2001 14:26, Berin Loritsch wrote: >> >>> I will commit it in the morning if all are in favor (it's on my machine >>> at work). >> > > > I don't know why that email didn't go through. Anyway, we have our > configuration > back to normal. Are there any more open issues that need to be resolved > _prior_ > to Avalon 4.1 release? > > * Configuration - Resolved > * ComponentValidator - On Hold > * Logger - Incorporated > * Developer's Docs - Updated > > > Pending any unresolved issues, Avalon Framework should now be considered in > Code Freeze. It will remain so until the weekend is over, and I will > make the > release on Monday. The only type of contributions that should be made to > Avalon 4.1 are documentation spelling fixes. The only types of changes to > the code should be Javadoc spelling fixes. > > We have the weekend to come up with any showstoppers, so fire away! > > > > -- "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin -- To unsubscribe, e-mail: For additional commands, e-mail: