From: Julien L. <ju...@fa...> - 2006-03-08 16:40:20
|
I'm changing the subject to something more concise. On 08/03/2006 15:56, kei...@nt... wrote: <snip> > However, my original objective for this thread > was to ask the MinGW Developer Community to give some attention to > the dozens, if not hundreds, of submitted patches languishing on > the SF Patch Tracker, which have not yet been assigned to any individual, > or indeed show no indication of having been reviewed in any way. I'm > calling for volunteers to assist in the review process, which must > precede the incorporation of accepted patches into the CVS, > wherever it > resides, before a nightly build can effectively deliver the patched > content to the users. > I don't have enough karma, but I'm willing to clean up some mSys related issues. I'll need tracker karma and mSys CVS karma. 1 - Some trackers and menu items are also useless, notably 'tasks', 'docs', 'screenshots' which can all be removed from sight. On a more challenging pace, and knowing that SF imposes some limitations on renaming categories and groups, the following would clean up a lot and impose a simplified yet performant bug tracking and feature request: 2 - trackers 'trackit', 'MSYS action items' can all be merged together into 'bugs' or 'feature requests'. To do that, we just duplicate the items in 'bugs' or 'feature request', and then remove the trackers 'trackit' and 'MSYS...' from sight. 3 - tracker 'patches' has always seemed overlapping both 'bugs' and 'feature requests'. A patch submitted is always to address either a bug or new feature. What were the guys at SF thinking when they created this ? If we ever get to clean out the whole list of pending patches, I think we could also remove this from sight or keep it for use just for developpers. Otherwise, there's some issues with the SF trackers, notably the 'group' choice box which either overlaps the 'category', or the 'resolution' box. I'm trying to figure out how to simplify this into something better and not some huge migrating process. 4 - ie: http://sourceforge.net/tracker/?func=detail&aid=1198530&group_id=2435&atid=102435 was committed to CVS. I could set "status=closed", but it doesn't reflect that it was committed in CVS but no new release was done. What would be good would not to have the 'resolution' box, and use the 'group' box as an advanced resolution box (none, invalid, valid, fixed in cvs, duplicate) With appropriate karma, I can clean up task 1 and 2. With appropriate karma and CVS karma, I can clean up some mSys related issues. (ie: http://sourceforge.net/tracker/?func=detail&aid=1352378&group_id=2435&atid=302435) 3 & 4 would need global approval, but I think it's worth it. For an example: http://sourceforge.net/projects/mshell/ Julien |