Goals for 4.0: Stability and Reliability

Created by: riyad

I think we should focus on stability, reliability and lessening the pain for administrators of GitLab. IMHO the following points should all be addressed before releasing 4.0 (delaying the release if necessary). Any PR/enhancement that is not aimed towards one of those goals should be postponed for the next release. Any issue/PR that needs to be closed before release should be assigned to the 4.0 milestone.

Information/Diagnosis

:no_entry::sweat: Create a proper about page (#1993)
✅ a rake task that gathers basic information (GitLab version, Gitolite version, distro, etc.) for copy and paste to issues (#2194)
✅ make gitlab:app:status task more useful, checking a lot more that now (e.g. are users in the right group, dir/file users/groups set correctly, dir/file permissions set correctly, Resque working, mailer working, cloning over http(s) working, ...) (#2004)
✅ for all checks offer instructions to fix them (#2266)

Platform

✅ make all tests work reliably
✅ make ProstgreSQL test work again
:no_entry::sweat: fix UI on IE (e.g. #1842 (closed), #2073 (closed))
✅ fix Resque integration (#2021 (closed))

Data integrity

🚧 revise all rake tasks to ask the user before irreversably changing DB/repos
✅ fix all current bugs for backup/restore and make it more reliable
❓ fix all open data loss bugs (e.g. #1621 (closed))

Documentation

✅ Revise all installation docs
✅ Revise/cleanup Wiki
✅ Revise Issue Submission Guide
✅ Revise Contribution Guide