make the staff client not clear the cache at startup, and provide a Clear Cache option on the login window for all builds

[Jason Etheridge]

Some staff would like the cache to persist to speed up first-runs of the staff client, yet other folks really like how clearing the cache helps with upgrades. A middle-ground might be to move the Clear Cache button on the login window from the developers' build to a menu entry under About for all builds, and then remove the automatic behavior.

[James Fournie (jfournie)]

I would like to see this.

Also, the "Clear Cache" in the Admin -> For Developers does not produce a confirmation dialog. Not sure if that's by design but it might be nice.

[Michael Peters (mrpeters)]

For what it's worth, 1.6.0.0 had the clear cache on the login screen. Our folks got really used to having it there and it kind of became an important debugging step when they'd get things like "authentication seed not found" errors. I'd love to see it returned there.

[Jason Stephenson (jstephenson)]

Michael, can you add a screen shot of what the 1.6.0.0 UI looked like for that button or describe it? Was it on a menu or on the login screen as a button by itself?

[Dan Scott (denials)]

Hi, we use "In Progress" to indicate that a committer is testing a proposed branch or patch, so I'm setting this back to the previous status until such time as the bug has been tagged "pullrequest" and a committer starts looking at it.

[Jason Stephenson (jstephenson)]

I've been using In Progress to mean any time someone is looking at something whether they're handling the pull request or writing the initial code.

I've removed the assignment to Pranjal, since I've not heard that he is actively working on this. If you are, then please reassign yourself.

[Kathy Lussier (klussier)]

Setting to Incomplete since this bug is specific to the xul client.