Our procedure at work also calls for paragraphs on "what you see" and "what you expected to see". The former is often some unexpected behavior or a stack dump, the latter is a short description of how you think your reproducer should work. Of course, we don't vet things as well, users can just put in any old thing they don't understand, so your first item about "bring it to the list" probably minimizes some of what I've mentioned.
On Sat, Mar 17, 2018 at 11:00 AM, Daniel Moody <[email protected]> wrote: > What about adding a requirement to paste the link to the scons users > archived thread in the submitted issue for reference and due process? > > On Sat, Mar 17, 2018, 1:54 PM Bill Deegan <[email protected]> > wrote: > >> Greetings, >> >> I've just added an issue creation template to Github. >> >> See it here: >> https://github.com/SCons/scons/blob/master/.github/issue_template.md >> >> If you have a moment to take a look and let me know if I've missed any >> information which should be provided when filing a new issue. >> >> Thanks, >> Bill >> SCons Project Co-Manager >> _______________________________________________ >> Scons-users mailing list >> [email protected] >> https://pairlist4.pair.net/mailman/listinfo/scons-users >> > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
