On Fri, Feb 10, 2023 at 10:48:25AM +0100, Michal Prívozník wrote: > On 2/10/23 10:34, Andrea Bolognani wrote: > > Hopefully including this request in ALL CAPITAL LETTERS in the > > issue template will cut down on the number of screenshots that > > end up cluttering bug reports by at least a tiny bit. > > > > Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> > > --- > > .gitlab/issue_templates/bug.md | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md > > index f220671a06..b923be0ca0 100644 > > --- a/.gitlab/issue_templates/bug.md > > +++ b/.gitlab/issue_templates/bug.md > > @@ -17,3 +17,4 @@ > > ## Additional information > > <!-- Attach XML configs, logs, stack traces, etc. Compress the files if necessary --> > > <!-- See https://libvirt.org/kbase/debuglogs.html on how to configure logging --> > > +<!-- Please DO NOT ATTACH SCREENSHOTS to the bug report. Provide all information as plain text --> > > Since we're changing our template, would it make sense to request users > to at least attempt to reproduce on something recent? I've seen reports > with ~3 years old libvirt. And given the pace libvirt's development is > moving it's very likely that the issue is fixed. And even if it wasn't - > we stop wasting our time trying to reproduce on current master only to > find out the issue was fixed a while ago. We already link to: https://libvirt.org/bugs.html#how-to-file-high-quality-bug-reports which could be expanded with a suggestion that reproducing on latest upstream would be beneficial, rather than cluttering up the issue template With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
