Please Identify which addons are banned in rejected github bug reports
#11
There are more reasons to want clean installs than only the banned add-ons, even though they do play a big part as @DarrenHill mentions. You get a new, fresh profile without any leftover cruft from updates, you have a fresh DB, no weird settings, no add-ons at all etc. It just helps a lot to narrow down where the problem lies. And you get reproduction steps that actually work from a clean install - which is all the developers have to go on to reproduce.

In a recent issue we finally got a reporter who claimed that he was quite sure MySQL had nothing to do with the problem to try on a clean install after some discussion, and - surprise, surprise - the issue was not present on a clean SQLite installation and appeared as soon as he put the MySQL DB back in. If he'd started with a clean install, we would have saved a lot of time dancing around the issue. A few devs wasted their time trying to reproduce the issue while it wasn't clear what was causing it and it would have easily been found with a clean install. Just as an example.
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average


Messages In This Thread
RE: Please Identify which addons are banned in rejected github bug reports - by yol - 2019-01-05, 11:57


Logout Mark Read Team Forum Stats Members Help
Please Identify which addons are banned in rejected github bug reports00