Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 39984 invoked by uid 500); 2 Feb 2003 19:18:15 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 39971 invoked from network); 2 Feb 2003 19:18:14 -0000 Message-ID: <001601c2caef$e7c6b8b0$0100a8c0@MAUCHI> From: "Ivelin Ivanov" To: References: <083201c2c931$a3b95d90$0100a8c0@MAUCHI> <3E3AA33B.8050406@verizon.net> <09b901c2c9a8$86290880$0100a8c0@MAUCHI> <3E3C4DD3.5040502@anyware-tech.com> Subject: Re: next Release of Cocoon Date: Sun, 2 Feb 2003 13:18:44 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > > > > > Ivelin, maybe I don't understand correctly the above, but why do you > want to fix bugs _if_ we announce a release ? I meant build problems, rather than functional bugs. Over the last 3 months I have fixed multiple times broken examples and links to the code that I contributed. These were usually caused by directory reorg or library updates. Ivelin --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org