From mint-bounce@lists.fishpool.fi Tue Dec 22 11:25:15 2009 Message-ID: <4B30F215.9040903@freesbee.fr> Date: Tue, 22 Dec 2009 17:21:41 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "mint@lists.fishpool.fi" Subject: Re: [MiNT] Bugtracker References: <1472E2BC2F174EEA94B8AC698BEABC39@mercatus.local> <4B2FB6ED.4020409@charter.net> <4B2FDE8E.6080907@online.no> <4B2FE9F4.8070409@charter.net> <4B30D255.1000007@freesbee.fr> <4B30DDB7.9000300@charter.net> In-Reply-To: <4B30DDB7.9000300@charter.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 091222-0, 22/12/2009), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nBMGPExs015470 Rob Mahlert a écrit : > I turned on Anonymous last night So I propose the following: 1) Everyone read the current list of bugs: http://sparemint.org/bugtracker/ 2) If someone knows a bug that is not on the Mantis list, register to Mantis and post a new bug. 3) If you have made a patch for a new feature, register to Mantis and post a new "bug" with the description of the feature you are adding, and your patch. Then it will be commented by other people, then committed by a maintainer. By doing this, everything related to a bug/evolution will be stored at the right place in Mantis. That way, we always have a list of the current features being worked on. What do you think about this ? -- Vincent Rivière