On Dec 28, 2010, at 7:38 AM, Frank H. Ellenberger wrote: > Hi, > > Am Samstag, 25. Dezember 2010 um 19:52:46 schrieb John Ralls: >> We also need to get the bug count down. There are almost 1000 of them open, >> and nearly half are more than 1 year old. A huge chunk of the older ones >> are enhancement requests which we should either add to the Roadmap or deny. > > I do not understand why the open enhancement requests are a problem except > for "nice" statistics. > > I think, the roadmap should show the general direction, while RFEs in > bugzilla > can also be small details. I often add entries there, which I would like to > improve later, may be next year. I would miss the reminder, if they would be > closed, because they do not fit in the roadmap. > > Just my 2ยข.
Some are small details, some are major changes. Some are good ideas, some not so much. With so many of them, it's a bit daunting to find the good ones worth implementing. The major changes (like your https://bugzilla.gnome.org/show_bug.cgi?id=570303) need to be in the roadmap if we're going to do them. There was a discussion on the user list last week about enhancement requests in which the users were directed to put them there because nobody looks back on the mailing list to find problems or enhancements... but if those users then look at bugzilla, they'll get the impression that nobody looks there, either. As for your personal to-do list, perhaps you could assign them to yourself. The three recent ones (that were waiting for the string freeze to lift) can be committed now. Going in the other direction, once we agree on the roadmap for the next version and who's going to do what, we can break each major task into a bunch of enhancements and set a developement release as the target. That's probably as close to project management as we're likely to get. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
