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

matrix-synapse: 0.99.3.2 -> 0.99.4 #61721

Merged
merged 1 commit into from May 21, 2019

Conversation

mguentner
Copy link
Contributor

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Please backport to 19.03

@Ekleog
Copy link
Member

Ekleog commented May 19, 2019

Thanks!

@GrahamcOfBorg build nixosTests.matrix-synapse

About the backport to 19.03, I'm not sure we should actually continue backporting all the updates. Now that the matrix protocol has stabilized, I'm starting to think we should backport only on security fixes (ideally only security fixes, but it requires more time…), like we do for other packages, as we no longer have the “synapse will just break if not updated” deadline. (disclaimer: I haven't checked the Changelog yet for security fixes, but there was nothing obvious)

cc @Ralith @roblabla @pacien for your opinion on this matter.

@mguentner
Copy link
Contributor Author

I agree, we can continue jumping some version that don't include a security issues.
That means 0.99.4 would not go into 19.03 but 0.99.4.1 might need to be backported, thus jumping 0.99.4.

@fadenb
Copy link
Contributor

fadenb commented May 20, 2019

we should backport only on security fixes

Basically every matrix-synapse release comes with a bunch of bugfixes. Is that not enough reason to backport (as long as it is not a major version change)?

@Ekleog
Copy link
Member

Ekleog commented May 21, 2019

@fadenb A bugfix is not necessarily a good thing to backport, as a bugfix can potentially break a user's workflow. This is for instance how debian handles stability (backport only the patches that fix security issues). On the other hand, the only current source of documentation for nixpkgs' backports (though it wasn't written with this aim, so this list was not actually the topic of the RFC) states that “patch-level and minor-level updates” should be backported. Whether 0.99.3.2 -> 0.99.4 is a minor update is an open question -- semver states that 0.x versions are all assumed to be incompatible. Also, basing our decisions on just version numbers would be plain wrong, given that projects don't all use semver.

All that to say, the policy around backports and what is acceptable breakage is currently quite fuzzy. If you feel like writing an RFC to clarify the situation, it would most likely help! Such an RFC would make clear what the acceptable level of breakage is, and which kinds of bugfixes should be backported (all security fixes, fixes when the program doesn't run at all… cosmetic fixes? also, how to handle the cases when we don't have enough manpower to manually extract just the wanted fixes, and will just bump the version).

For now, until someone comes up with a concrete “my synapse breaks and wouldn't with this update” case (or if there's a security fix), I don't feel comfortable backporting this commit :)

@Ekleog Ekleog merged commit afd8f69 into NixOS:master May 21, 2019
@mguentner mguentner deleted the matrix_synapse_0.99.4 branch May 21, 2019 09:16
@mguentner mguentner mentioned this pull request May 22, 2019
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants