call for testing: quassel-webserver

[Leo Arias]

Thanks to everybody who has been testing.

I think this is a good story of how snaps are making it easier for
testers and upstream developers to collaborate.
Some time ago the developer of quassel-webserver told me that it was
ready to be tested by the wider community. I made a quick test and it
was getting stuck, so I reported this bug:
https://github.com/magne4000/quassel-webserver/issues/220

The dev said that it was working for him. I tested it in all my
machines and my VMs and I just couldn't understand how it was working
for him but failing everywhere for me. So I asked a few people to give
it a try. The steps to reproduce were super simple, and by installing
it from a snap all of us trying it were in a pretty similar
environment. One of them confirmed the bug, which convinced the
developer to dig deeper. He fixed it, and the following day he was
ready to make a release candidate.

Now quassel-webserver 2.2.7 is in the candidate channel, and everybody
who had 2.2.6 installed will get the automatic update soon, without
doing anything else. Please check if you already have the new version,
test it a little, and if you find something weird, file a bug directly
upstream: https://github.com/magne4000/quassel-webserver/issues/new

We are polishing all these workflows so upstream developers get super
fast feedback from early adopters, and everything it takes for them is
to write a simple snapcraft.yaml file, and for us to run a simple snap
install command.

If you have ideas of how to improve the process, or any features you
would like to see, please let us know.

pura vida.