You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
evan-forbes opened this issue
Sep 11, 2023
· 1 comment
Labels
proposalitem is not yet actionable and is suggesting a change that must first be agreed upontestingitems that are strictly related to adding or extending test coverage
Similar to having the ability to specifiy an increment to the app version in the binary or a config, we should also have the ability to decrement the app version. This might already be mostly possible, but we should add tests if that's the case.
The text was updated successfully, but these errors were encountered:
to update the most recent thinking around this proposal, the app version should likely only incremented. The main reason being that downgrades would require any state migrations to be backwards compatible, which would require a rather insane amount of testing to have full confidence in. If a specific portion or entirety of an upgrade can be confirmed to be causing a specific regression, then the app version should be incremented to apply or revert those changes.
proposalitem is not yet actionable and is suggesting a change that must first be agreed upontestingitems that are strictly related to adding or extending test coverage
Similar to having the ability to specifiy an increment to the app version in the binary or a config, we should also have the ability to decrement the app version. This might already be mostly possible, but we should add tests if that's the case.
The text was updated successfully, but these errors were encountered: