Bugzilla – Activity log for bug 5711: old js files can be cached after upgrade
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | New Account
- | Log In
- | Forgot Password
Back to bug 5711
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| astrand | 2015-11-10 10:34:36 CET | Target Milestone | --- | NearFuture |
| samuel | 2017-01-26 12:03:27 CET | Target Milestone | MediumPrio | --- |
| cromptonra | 2017-01-26 13:42:30 CET | CC | cromptonra | |
| ossman | 2017-01-31 10:35:11 CET | Target Milestone | --- | PoolTodo |
| ossman | 2019-09-18 13:08:37 CEST | Target Milestone | PoolTodo | MediumPrio |
| martin.ostlund | 2021-08-19 14:10:32 CEST | CC | martin.ostlund | |
| ossman | 2022-03-24 12:56:21 CET | See Also | https://www.cendio.com/bugzilla/show_bug.cgi?id=7391 | |
| samuel | 2022-10-07 14:16:29 CEST | See Also | https://bugzilla.cendio.com/show_bug.cgi?id=8000 | |
| alexander.zeijlon | 2025-01-23 14:57:38 CET | Target Milestone | MediumPrio | 4.19.0 |
| CC | alexander.zeijlon | |||
| alexander.zeijlon | 2025-01-23 14:57:47 CET | Assignee | samuel | alexander.zeijlon |
| adaha | 2025-01-27 12:24:00 CET | CC | adaha | |
| alexander.zeijlon | 2025-01-27 13:00:51 CET | Acceptance Criteria | MUST: * Users shouldn't get a dysfunctional web client after a server upgrade due to a stale browser cache. * The web client should be usable in terms of fetching files in non-optimal scenarios, w.r.t latency and bandwidth. SHOULD: * Users shouldn't get a dysfunctional web client after a server downgrade due to a stale browser cache. |
|
| alexander.zeijlon | 2025-01-27 15:36:23 CET | Resolution | --- | FIXED |
| Status | NEW | RESOLVED | ||
| alexander.zeijlon | 2025-01-28 08:27:51 CET | Acceptance Criteria | , w.r.t latency and bandwidth. SHOULD: * Users shouldn't get a dysfunctional web client after a server downgrade due to a stale browser cache. MUST: * Users shouldn't get a dysfunctional web client after a server upgrade due to a stale browser cache. * The web client should be usable in terms of fetching files in non-optimal scenarios | client should be usable in terms of fetching files in non-optimal scenarios, w.r.t latency and bandwidth. MUST: * Users shouldn't get a dysfunctional web client after a server upgrade due to a stale browser cache. SHOULD: * Users shouldn't get a dysfunctional web client after a server downgrade due to a stale browser cache. * The web |
| alexander.zeijlon | 2025-01-28 08:55:20 CET | Keywords | relnotes | |
| adaha | 2025-01-28 10:39:43 CET | Keywords | adaha_tester | |
| Acceptance Criteria | MUST: * Users shouldn't get a dysfunctional web client after a server upgrade due to a stale browser cache. SHOULD: * Users shouldn't get a dysfunctional web client after a server downgrade due to a stale browser cache. * The web client should be usable in terms of fetching files in non-optimal scenarios, w.r.t latency and bandwidth. | MUST: * Users should get a functional web client after a server upgrade. SHOULD: * EXTRA: * Users should get a functional web client after a server downgrade. |
||
| adaha | 2025-01-28 11:09:16 CET | Acceptance Criteria | MUST: * Users should get a functional web client after a server upgrade. SHOULD: * EXTRA: * Users should get a functional web client after a server downgrade. | MUST: * Users shouldn't get a dysfunctional web client after a server upgrade due to a stale browser cache. SHOULD: * Users shouldn't get a dysfunctional web client after a server downgrade due to a stale browser cache. * The web client should be usable in terms of fetching files in non-optimal scenarios, w.r.t latency and bandwidth. |
| adaha | 2025-01-28 14:57:45 CET | Status | RESOLVED | CLOSED |
Back to bug 5711