I agree with Paul
What I would like to see is NO TODO file. Instead, let's move
everything to the tracker. If the tracker doesn't let us setup
roadmaps and versions, then let's switch trackers. SF.net provides
optional Mantis and Trak trackers now.
Just a thought. A tracker system is designed for this stuff. Have 4
diverged TODOs amongst several branches is not well fitted. I think
TODO is reasonable only in experimental branches where you want to
make a note because you are half-way through implementing a feature.
Anyways, thanks for your effort Andy. we needed it organized in any case.
On 8/11/09, Andy Kelley <email@example.com> wrote:
> I was hoping you would consolidate the versions and everything. You're
> really the only person who can decide those things.
> I agree we have too much effort duplication as far as TODO goes. We need to
> eliminate 2 of our 3 TODO/bug/roadmap trackers and stick with one.
> On Tue, Aug 11, 2009 at 5:04 AM, Tobias Doerffel
>> Am Dienstag, 11. August 2009 12:04:34 schrieb Andy Kelley:
>> > I went ahead and organized the TODO list in this way. It's pushed to
>> > and here is a preview:
>> > Tobias is really the one who needs to assign TODO items to version
>> > but hopefully this is a good start. I hope you guys like this idea, I
>> > it will help direct LMMS in an efficient and powerful way.
>> Thanks for your initial effort. I'll improve the assignments between items
>> versions and also remove items, that are out of date. At the same time I'm
>> annoyed by the overall structure: we have a TODO-List/Roadmap in Wiki, we
>> a TODO file in Git (diverging in various branches) - both of them contain
>> reports which belong to the bug tracker. The feature tracker lists items,
>> can be found both in the TODO file as well as in the Wiki... it's a mess
>> Anyways I'll commit and push an updated TODO soon, so please don't touch
>> file in the meantime.
>> Just a note on versioning: 0.4.x is a stable series, i.e. all changes
>> be bugfixes / really minor improvements that do not introduce regressions.
>> therefore won't do any refactoring in this series. What can't be fixed
>> trivial patches won't get fixed in 0.4.x.
>> 0.9.x is just a name for the current developer series - there won't be any
>> 0.9.x releases (except for 1.0 alpha1=0.9.70, 1.0 beta1=0.9.80, 1.0
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> trial. Simplify your report design, integration and deployment - and focus
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> LMMS-devel mailing list
> Andy Kelley
> Nuclear Development