From mint-bounce@lists.fishpool.fi Sun May 30 04:19:22 2010 X-Virus-Scanned: Debian amavisd-new at pp.htv.fi From: Eero Tamminen Organization: Koti To: mint@lists.fishpool.fi Subject: Re: [MiNT] MiNTLib / Kernel Future and also SpareMiNT..... Date: Sun, 30 May 2010 11:17:59 +0300 User-Agent: KMail/1.9.9 References: <201005301048.54254.oak@helsinkinet.fi> <4C021D02.3090403@online.no> In-Reply-To: <4C021D02.3090403@online.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201005301117.59307.oak@helsinkinet.fi> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: oak@helsinkinet.fi Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hi, On Sunday 30 May 2010, Jo Even Skarstein wrote: > On 05/30/2010 09:48 AM, Eero Tamminen wrote: > > There could be two pages. One "wishes for kernel" that is open for > > everyone and another one a roadmap which is closed for editing (could > > come e.g. from version control). > > The roadmap belongs in the bugtracker. So does the feature list. If > these systems are kept separate, it's much more work to move features > from the wish-list to the roadmap and then into the bugtracker. Right! That's a much better way to work than what I suggested. :-) One can also open a bugzilla entry for a new feature just to tell that he's working on one and attach a patch to integrate once its ready. > A bugtracker tool ('bugtracker' is really not a good name, as it's used to > manage features as well) makes life a lot easier if you have a long term > plan with the project. Well, bug can be "doesn't to X". Or would "issue" be better name for that than "bug"? - Eero