Summary: | software system windows ussualy crashed ( | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kpackagekit | Reporter: | Alexander Serdts <serdtsev> |
Component: | general | Assignee: | Steven M. Parrish <smparrish> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andrew.crouthamel, dantti12, grgoffe |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Alexander Serdts
2011-04-07 14:23:38 UTC
*** Bug 262001 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Andrew, I see that this bug was reported in 2011! Why is that? I would suggest that bugs older than a year be closed automatically with a request for more info needed... like, "Is this bug still happening". I think it's a big waste of everyone's time and energy to spend time on these old bugs. George... Hi George, while I agree with you, there are a number of people within KDE that have the opposite opinion. So, I'm doing my best to follow follow up on these old bugs, while trying to keep everyone happy. Andrew, Thanks for your help. I would point to this bug as evidence to the wast of time statement. Again, bugs with NO activity for N years should go through an automatic closure process... i.e., contact the user and/or the developer and/or maintainer and give them one more chance to avoid the closure. In any event... Best regards, George... (In reply to George R. Goffe from comment #5) > Andrew, > > Thanks for your help. > > I would point to this bug as evidence to the wast of time statement. > > Again, bugs with NO activity for N years should go through an automatic > closure process... i.e., contact the user and/or the developer and/or > maintainer and give them one more chance to avoid the closure. > > In any event... Best regards, > > George... Just FYI, the NEEDSINFO status I placed this in, will cause it to auto-close in 30 days with no response. :) Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |