Originally published at: https://nextcloud.com/blog/help-test-nextcloud-12.0.3/
It is that time again: we’re gearing up for bugfix releases and we’re looking for your help to ensure a smooth upgrade experience for all our users again! As before, we’re offering a little incentive in the form of a Nextcloud t-shirt for anyone who discovers and reports a bug in the upgrade process or a regression from 12.0.x.
Testing testing testing
The Nextcloud 12.0.3 milestone has closed nearly 70 issues,
with over 170 commits fixing small problems and bringing minor improvements all over. While that makes it smaller than 12.0.2 it is still a significant release and we'd like to give it a good run through our testing process. Of course, every change goes through automated code level testing and a review process but nothing beats real life experiences gathered by our wider community. No testing matrix can cover all the different ways in which you all use Nextcloud with unique combinations of databases, operating systems, file systems, network settings and more!
We’re still aware of one open issue, which is that the latest update of the Calendar app (1.5.4) triggers a spurious warning of the file integrity checker. It complains that a file is missing:
.gitignore. You can ignore this warning, we’re working on getting an update to the Calendar app in the store which will eliminate it.
Video showing upgrade to the first release candidate and the calendar problem.
To test the upgrade to 12.0.3RC2, follow these steps:
- Backup your database:
mysqldump --single-transaction -h [server] -u [username] -p[password] [db_name] > …/nextcloud-sqlbkp_ (see our documentation for other databases and here for restoring if needed)
- Set your release channel to beta in the web interface
- run the updater from the Nextcloud folder:
sudo -u [webserver username] updater/updater.phar
If all goes well, you should soon be able to log into a fresh Nextcloud on your webserver! Report any problems you encounter beyond the known file integrity check problem so we can fix them for the final release. And remember, if you find a bug, report it! The first reporter for each distinct upgrade issue or regression from 12.0.x (a function that worked in an earlier 12.0.x release but is broken in 12.0.3RC) that is found earns a t-shirt.