Return-Path: Delivered-To: apmail-xml-security-dev-archive@www.apache.org Received: (qmail 86158 invoked from network); 17 Oct 2005 10:38:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Oct 2005 10:38:28 -0000 Received: (qmail 63503 invoked by uid 500); 17 Oct 2005 10:38:27 -0000 Delivered-To: apmail-xml-security-dev-archive@xml.apache.org Received: (qmail 63491 invoked by uid 500); 17 Oct 2005 10:38:27 -0000 Mailing-List: contact security-dev-help@xml.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: Reply-To: security-dev@xml.apache.org List-Id: Delivered-To: mailing list security-dev@xml.apache.org Received: (qmail 63480 invoked by uid 99); 17 Oct 2005 10:38:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Oct 2005 03:38:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [194.128.225.190] (HELO spmler1.mail.eds.com) (194.128.225.190) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Oct 2005 03:38:27 -0700 Received: from spmlir2.mail.eds.com (spmlir2.mail.eds.com [205.191.69.42] (may be forged)) by spmler1.mail.eds.com (8.13.2/8.12.10) with ESMTP id j9HAc2Dp011751 for ; Mon, 17 Oct 2005 11:38:05 +0100 Received: from spmlir2.mail.eds.com (localhost.localdomain [127.0.0.1]) by spmlir2.mail.eds.com (8.13.4/8.12.10) with ESMTP id j9HAbMNA006285 for ; Mon, 17 Oct 2005 11:37:22 +0100 Received: from ukspm010.emea.corp.eds.com ([204.230.90.155]) by spmlir2.mail.eds.com (8.13.4/8.12.10) with ESMTP id j9HAbMsL006280 for ; Mon, 17 Oct 2005 11:37:22 +0100 Received: from ukspm204.emea.corp.eds.com ([204.230.90.193]) by ukspm010.emea.corp.eds.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 17 Oct 2005 11:37:22 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: To Bugzilla or Not?? Date: Mon, 17 Oct 2005 11:37:22 +0100 Message-ID: <4F014656062C1140880B2247EDAFD3B102E07507@ukspm204.emea.corp.eds.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: To Bugzilla or Not?? Thread-Index: AcXPMuSRzY/2sH68R4C3Z1UQsAr/AgBb8lpAAAdmyTAABSSJEAAqAmKQAGIdFKA= From: "Cullum, Steve" To: X-OriginalArrivalTime: 17 Oct 2005 10:37:22.0308 (UTC) FILETIME=[C1B55C40:01C5D306] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, I recently posted to this mailing list with some comments regarding memory leaks and VS project workspaces with XSEC. I don't want these issues to go unnoticed, however in my case I am unsure if they warrant using bugzilla. Is posting on this mailing list sufficient? It is my understanding that bugzilla is only to be used for serious bugs; what constitutes serious, is there a list of bug category's I can use as a guideline? Hope this posting makes sense.. I just don't want to break the protocol ! Thanks Steve