From axis-c-dev-return-163-apmail-ws-axis-c-dev-archive=ws.apache.org@ws.apache.org Sat Feb 28 02:36:53 2004 Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 93510 invoked from network); 28 Feb 2004 02:36:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 28 Feb 2004 02:36:53 -0000 Received: (qmail 68400 invoked by uid 500); 28 Feb 2004 02:36:33 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 68383 invoked by uid 500); 28 Feb 2004 02:36:33 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 68320 invoked from network); 28 Feb 2004 02:36:32 -0000 Received: from unknown (HELO relay.pair.com) (209.68.1.20) by daedalus.apache.org with SMTP; 28 Feb 2004 02:36:32 -0000 Received: (qmail 41020 invoked from network); 28 Feb 2004 02:36:40 -0000 Received: from unknown (HELO IBM3F7R4BUUQ6D) (203.94.84.117) by relay.pair.com with SMTP; 28 Feb 2004 02:36:40 -0000 X-pair-Authenticated: 203.94.84.117 Message-ID: <0e0301c3fda3$adbc4800$02c8a8c0@watson.ibm.com> From: "Sanjiva Weerawarana" To: "Apache AXIS C Developers List" References: <7D5800A5B6E26644B2EB7A862856B0D40EBAC9AE@SARASWATI> <063601c3fc41$9d5f5410$02c8a8c0@watson.ibm.com> <1077826777.30435.8.camel@charlotte.samlang.net> Subject: Re: how to send a patch Date: Sat, 28 Feb 2004 08:36:31 +0600 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4927.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N "Sam Lang" writes: > > On a side note I'm curious about the AxisC++ process of accepting bugs. > Who gets what and assigns them to the appropriate people? > > -Sam As an open-source project there is no one person "in charge" who assigns bug fixing or other work to specific developers. Bugs are picked up by developers who want to work on those bugs; it may seem too damned chaotic to work but it does work. Yes, it often does take longer than if the project were fully managed under the cathedral model but that's not how open source works. When a release time comes up the release manager does play the role of the "one guy in charge", at least for the duration of that release. During the release planning process the specific bugs to be fixed are identified (and recorded in the release plan document) and then once that's committed the release does not go thru until those bugs are fixed. The release manager uses all the techniques he can to get the bugs fixed .. and since the release is occurring because the developers want it released (and because the release manager is also a developer) the bugs do indeed get fixed. Sanjiva.