|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| = Overview =
| | Moved to https://github.com/mozilla/gecko-dev/blob/master/devtools/docs/backward-compatibility.md |
| | |
| When making changes to the DevTools, there are certain backward compatibility requirements that we should keep in mind.
| |
| | |
| In general, we should strive to maintain feature support for existing servers as we continue to make changes to the code base. At times, this can be difficult to achieve, however.
| |
| | |
| = Specific Guidelines =
| |
| | |
| The important compatibility scenarios are:
| |
| | |
| # Nightly desktop client MUST maintain existing compatibility with Gecko 28 and later servers
| |
| #* This is needed for supported Firefox OS simulators (1.3+)
| |
| # Nightly desktop client SHOULD maintain existing compatibility back to release channel servers
| |
| #* This is mainly to simplify cross-platform use cases, i.e. desktop Nightly with release Fennec
| |
| #* Scenario 1 above currently implies greater compatibility than this one anyway
| |
| | |
| Certainly when a new feature needs a new actor method to function, it won't work with servers that don't support it. But we should still ensure the client doesn't explode when using unrelated, existing features, at least until the above time windows have elapsed.
| |
| | |
| = Testing =
| |
| | |
| The harder part of this currently is that there is no automated testing to ensure the above guidelines have been met. While we hope to have this at some point, for now manual testing is needed here.
| |
| | |
| The easiest way to test this is to check your work against the Firefox OS 1.3 simulator to ensure existing features in the area you are changing continue to function. That doesn't cover every case, but it's a great start.
| |