On Thu, 26 Jun 2003 12:45:15 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> ML> Anything that is of a "wishlist" / "feature request" will for > the > ML> moment be ignored. Stability / making current stuff work comes > first > ML> over adding new stuff. Does that seem reasonable? > > Yes and no. In general, bugs should, of course, be fixed before > adding new > features but as the example of a composer shows, sometimes it is > easier and > better to add a new feature (new composer) than fix the bugs in the > old > code. <Sigh> What do you guys use for a wrapping setting? I think I'm at about 70 or so. Anyway, OK, I agree with what you say above. If we replace an entire sub-system like composer and as a side effect fix a bunch of bugs, that is OK and desireable. Existing process Re-engineering with a superior outcome is good. What I think is not OK is to go out and say implement the getting of mail via HTTP which is a functionality which is clearly not there now even slightly. Does that make sense? > ML> I am completely ignoring stuff in the CVS TODO list / other text > ML> files. Thats Vadim's problem LOL ;-) > > Yes, right. TODO is more than 4 years old, too... > > ML> I will have to experiment as to the rate of assigning stuff. I > ML> certainly am not aiming for a Bug du jour but maybe closer to a > bug du > ML> (what is week?). > > Semaine :-) Anyhow, the rate is not important, what is important > is to get > the clear list of bugs (for each person which basically means > Xavier and me > right now) in the order of priorities. Absolutely agree. I have gone through my mini-tree and sorted out which are clearly asking for new, not currently existing functionality. My next task is to look at what is left and try to divide the bugs into sub systems where possible allong the lines of the current component breakdown in the buglist. To me, it makes good sense to fix one sub system at a time as much as possible. Yes, I know there is some overlap between all components but I think you know what I mean. I know also you have said in another message that you have a bunch of other priorities till mid July so I shall look for small stuff for now and leave "Replace XXXX" type stuff for later. Fixing lots of small bugs closes just as many bug reports as REPLACE XXX does for it's relevant bugs. TIA Dr. QA ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
