|
In the year 2012 there was an unnice experience with differend versions of Eclipse/CDT, therefor a report was written : https://bugs.eclipse.org/bugs//show_bug.cgi?format=multiple&id=394094 Today its is somehow a historic problem: Or at least I didn't test the samething with currect versions. I only want to now, if all of those old bugs should be handled like solved or like closed? |
Replies: 1 comment
|
Old Bugzilla reports should not be treated as automatically solved. CDT's GitHub migration notes say that GitHub issues replaced Bugzilla, but old Bugzilla bugs were not batch-migrated. Bugzilla is kept as a read-only historical record, and still-relevant bugs can be moved to GitHub issues case by case. So for that 2012 report, I would treat it as historical unless someone can still reproduce it on a supported CDT/Eclipse version. If it still reproduces, the useful next step is a new GitHub issue with the old Bugzilla link, the tested CDT/Eclipse versions, and a fresh reproduction. If it no longer reproduces or nobody can retest it, it is better left as archived history rather than assumed fixed. |
Old Bugzilla reports should not be treated as automatically solved.
CDT's GitHub migration notes say that GitHub issues replaced Bugzilla, but old Bugzilla bugs were not batch-migrated. Bugzilla is kept as a read-only historical record, and still-relevant bugs can be moved to GitHub issues case by case.
So for that 2012 report, I would treat it as historical unless someone can still reproduce it on a supported CDT/Eclipse version. If it still reproduces, the useful next step is a new GitHub issue with the old Bugzilla link, the tested CDT/Eclipse versions, and a fresh reproduction. If it no longer reproduces or nobody can retest it, it is better left as archived history rather than assume…