diff options
| author | Lukas Reschke <lukas@owncloud.com> | 2016-02-27 15:42:06 +0100 |
|---|---|---|
| committer | Lukas Reschke <lukas@owncloud.com> | 2016-02-27 15:42:06 +0100 |
| commit | 348717c4ec6d4fa7f6f81f9fae5b8b38a19eb88b (patch) | |
| tree | 4cdca05863bd278eefbba24e7429ee6be6e393ba /issue_template.md | |
| parent | f9826ec9486c6a4e6a55b8985ba677a4f066af3b (diff) | |
| download | nextcloud-server-348717c4ec6d4fa7f6f81f9fae5b8b38a19eb88b.tar.gz nextcloud-server-348717c4ec6d4fa7f6f81f9fae5b8b38a19eb88b.zip | |
Add question from where ownCloud was enabled
With regard to the following patch in Debian I'd recommend that we add to the issue template that we ask where users got their ownCloud from.
This is super dangerous stuff from Debian again. Can't call it otherwise. With 9.0 we can detect that since the question for the code integrity would return "Not enabled" instead of passed. But unluckily this is already 8.2.
(while skipping one version *might* work it is completely untested and I smell already users reporting very hard to debug bugs to us => Waste of time)
https://sources.debian.net/src/owncloud/8.2.2~dfsg-1/debian/patches/0009-Don-t-stop-update-over-several-major-versions.patch/
Diffstat (limited to 'issue_template.md')
| -rw-r--r-- | issue_template.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/issue_template.md b/issue_template.md index e19583977ef..c6744e6014a 100644 --- a/issue_template.md +++ b/issue_template.md @@ -29,6 +29,8 @@ Tell us what happens instead **Updated from an older ownCloud or fresh install:** +**Where do you installed ownCloud from:** + **Signing status (ownCloud 9.0 and above):** ``` |