Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider regression testing against the last N versions of Synapse, plus develop #12545

Open
turt2live opened this issue Feb 26, 2020 · 0 comments
Labels
P2 T-Enhancement T-Task Tasks for the team like planning

Comments

@turt2live
Copy link
Member

Ideally as other server implementations become popular we just add to our regression tests, but for now Synapse holds the market share.

With an initial suggestion of N being 3 minor versions (1.x series, not patch versions) plus one for develop we could catch bugs in upcoming releases of Synapse and ensure our upcoming release is backwards compatible too.

This should be automated and happen concurrently with a deploy to /develop (so we don't block features behind an hour of regression tests). We could also run them nightly with the electron stuff, but again we shouldn't block the electron nightlies from publishing because of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 T-Enhancement T-Task Tasks for the team like planning
Projects
None yet
Development

No branches or pull requests

1 participant