Hello, I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!). -- Dries Buytaert :: http://www.buytaert.net/
Yay! +1 Dries. --Larry Garfield On Wed, January 25, 2006 3:20 pm, Dries Buytaert said:
Hello,
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
-- Dries Buytaert :: http://www.buytaert.net/
On 25 Jan 2006, at 22:20, Dries Buytaert wrote:
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement. -- Dries Buytaert :: http://www.buytaert.net/
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement.
Excellent! It's nice to see only one CVS version listed on the submit issue page :) Housecleaning: Is it possible to rename 'cvs' to 'cvs/head' ? or 'CVS/HEAD'? And adding a description for each field or linking to a page with an explanation of the fields/terminology will be very useful as well.. Critical vs. Normal vs. Minor etc. Thanks, -K
Dries Buytaert wrote:
On 25 Jan 2006, at 22:20, Dries Buytaert wrote:
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement.
21:44 < killes> Dries_: please remove all releases older than 4.5, all non-4.7 RCs and betas. 21:45 < Dries_> killes: reply by mail, please (otherwise I loose track) Cheers, Gerhard
On 26 Jan 2006, at 22:39, Gerhard Killesreiter wrote:
Dries Buytaert wrote:
On 25 Jan 2006, at 22:20, Dries Buytaert wrote:
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement.
21:44 < killes> Dries_: please remove all releases older than 4.5, all non-4.7 RCs and betas. 21:45 < Dries_> killes: reply by mail, please (otherwise I loose track)
What to do with the issues associated with those releases? -- Dries Buytaert :: http://www.buytaert.net/
Dries Buytaert wrote:
On 26 Jan 2006, at 22:39, Gerhard Killesreiter wrote:
Dries Buytaert wrote:
On 25 Jan 2006, at 22:20, Dries Buytaert wrote:
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement.
21:44 < killes> Dries_: please remove all releases older than 4.5, all non-4.7 RCs and betas. 21:45 < Dries_> killes: reply by mail, please (otherwise I loose track)
What to do with the issues associated with those releases?
Update them to be against cvs, autogenerate a list of them, and ask people to check if they still apply. Or just "won't fix" them. :p Cheers, Gerhard
-- Dries Buytaert :: http://www.buytaert.net/
What to do with the issues associated with those releases?
Update them to be against cvs, autogenerate a list of them, and ask people to check if they still apply. Or just "won't fix" them. :p
Won't fix. I will stop fixing core bugs if I need to wade through 4.3beta issues marked as CVS.
Op donderdag 26 januari 2006 22:17, schreef Karoly Negyesi:
Won't fix. I will stop fixing core bugs if I need to wade through 4.3beta issues marked as CVS.
Wont fix, indeed. When I wade trough the (very) old bugs, approx 80% of them are actually duplicate, fixed or won't fix. Is it possible to mail out the status changes of each issue to subscribed people? That way all people who feel like it, can re-open them. If someone takes the hassle of re-opening, it must be a real bug! Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
On 1/27/06, Bèr Kessels <ber@webschuur.com> wrote:
Op donderdag 26 januari 2006 22:17, schreef Karoly Negyesi:
Won't fix. I will stop fixing core bugs if I need to wade through 4.3beta issues marked as CVS.
Wont fix, indeed. When I wade trough the (very) old bugs, approx 80% of them are actually duplicate, fixed or won't fix.
Is it possible to mail out the status changes of each issue to subscribed people? That way all people who feel like it, can re-open them. If someone takes the hassle of re-opening, it must be a real bug!
This is standard policy in the Mozilla project to simply "wontfix" any bugs that are older than a certain amount and haven't had a new comment in a certain number of months - occasionally controversial, but standard and eventually the people who dislike it end up liking it. They have a similar problem with the "is this CVS from 2002 or CVS from 2006" situation, but I they use "trunk" or specify which branch it is on. Then, when they make a new branch bugs (try to) get reviewed and split between that new branch and trunk. Greg
At 10:24 AM +0100 27/1/06, Bèr Kessels wrote:
Wont fix, indeed. When I wade trough the (very) old bugs, approx 80% of them are actually duplicate, fixed or won't fix.
I have read every issue filed against the menu system and closed all the ones that are obsolete. There are still 8 active issues older than 6 months and they are all still real issues. Minor, but real. I don't want these old issues against the menu system to be closed. I would also like them to retain their current timestamp so I can easily see that they are old. I think it is lazy to simply wontfix these old issues. It takes only a couple of minutes to identify issues that have already been fixed. Duplicates are harder to match up, but that's no excuse for mass deletion of a lot of valid issues. ...Richard.
I think it is lazy to simply wontfix these old issues. It takes only a couple of minutes to identify issues that have already been fixed. Duplicates are harder to match up, but that's no excuse for mass deletion of a lot of valid issues.
we have lived with this clutter for years. lets be pragmatic. noone is going to wade through the whole drupal project to fix old issues. noone did it in the last 3 years, and noone is likely to do it in the next 3 years. if you don't want old issues to change status on you, then associate them with a modern release. thats all. no timestamp change. it is not like we are deleting the issues.
Op vrijdag 27 januari 2006 21:52, schreef Moshe Weitzman:
if you don't want old issues to change status on you, then associate them with a modern release. thats all. no timestamp change. it is not like we are deleting the issues.
And in addition, I found that after a closing frenzy of mine, some people rushed in and reopened them! great: those issues are really issues. But a vast mayority of the issues that i commented "please re-open if you still have this problem, or otherwise feel this is still an issue" is never ever opened. I expect the mayority of these notes is not even read! So, if there are five valid isssues on menu, we should bookmark them now, or else post a "bump". so that they can eitehr be reopened or are not closed at all. You really don't want to know what you come across when you "start at the bottom" closing issues. Its madness. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
At 10:02 PM +0100 26/1/06, Dries Buytaert wrote:
21:44 < killes> Dries_: please remove all releases older than 4.5, all non-4.7 RCs
What to do with the issues associated with those releases?
Change the release to 4.5 for all pre-4.5 releases. I assume there will be a comment added to the issue recording the change. ...Richard.
On Thu, 2006-01-26 at 22:02 +0100, Dries Buytaert wrote:
On 26 Jan 2006, at 22:39, Gerhard Killesreiter wrote:
Dries Buytaert wrote:
On 25 Jan 2006, at 22:20, Dries Buytaert wrote:
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement.
21:44 < killes> Dries_: please remove all releases older than 4.5, all non-4.7 RCs and betas. 21:45 < Dries_> killes: reply by mail, please (otherwise I loose track)
What to do with the issues associated with those releases?
-- Dries Buytaert :: http://www.buytaert.net/
If they're that old, and haven't been fixed... I think its safe to assume won't fix... If its important to someone I'd expect them to question the status.
On 26 Jan 2006, at 21:35, Dries Buytaert wrote:
I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!).
To continue the house-cleaning, I intend to remove some old releases. If you look at http://drupal.org/project/issues/search/ drupal, you'll see that there are some releases that could do with being removed or merged. Examples: '4.3.0-rc', '4.5.0-rc', etc. Suggestions are welcome. If not, I'll proceed based on my own judgement.
Did some preliminary research: there are currently 1841 active bugs (does not include tasks or feature requests) across all projects (not just the Drupal project). If I were to mark all active bugs that have not been touched in the past year as 'fixed', we'd close 146 issues. If I set the threshold to 9 months, we'd be closing 357 issues instead. Not an awful lot so I think we are doing reasonably well ... :) -- Dries Buytaert :: http://www.buytaert.net/
participants (11)
-
Bèr Kessels -
Darrel O'Pry -
Dries Buytaert -
Dries Buytaert -
Gerhard Killesreiter -
Greg Knaddison -
Karoly Negyesi -
Karthik -
Larry Garfield -
Moshe Weitzman -
Richard Archer