Revise GitHub templates #12574

FranciscoPombal · 2020-04-21T18:38:48Z

Add a checklist and guidance comments

Separated from #11896 for easier review.

Previews:

Selection screen after clicking "New issue"

Click to show
Bug report

Click to show
Feature request

Click to show

xavier2k6 · 2020-04-21T19:16:59Z

Does this or the other PR #11896 close #8330?

FranciscoPombal · 2020-04-22T00:57:43Z

@xavier2k6 technically, that issue should have been closed with the merging of the linked PR in the last comment (fixed that now). These new PRs are just follow-ups that improve on that original ones, that arose from my additional experience in managing the issue tracker.

.github/ISSUE_TEMPLATE.md

LordNyriox · 2020-04-23T17:33:08Z

@FranciscoPombal: Not strictly related to the PR itself, but I noticed that both the old template and this one do not seem to have a defined layout for "feature requests".

For instance, submitting a log entry for a behavior that does not yet exist, does not seem viable to me.

Any advice on this?

FranciscoPombal · 2020-04-23T18:48:03Z

@FranciscoPombal: Not strictly related to the PR itself, but I noticed that both the old template and this one do not seem to have a defined layout for "feature requests".

For instance, submitting a log entry for a behavior that does not yet exist, does not seem viable to me.

Any advice on this?

Ok, I have changed things around a bit. Now there are separate templates for bug reports and feature requests, as well as links to the relevant support communities. Additionally, I threw in a simple PR template. When a user clicks "New issue", now they will get something similar to this this: https://github.com/microsoft/TypeScript/issues/new/choose

As a bonus, GitHub will no longer complain about "You are using an old version of issue templates. Please update to the new issue template workflow. Learn more" (check this here: https://github.com/qbittorrent/qBittorrent/blob/master/.github/ISSUE_TEMPLATE.md)

FranciscoPombal · 2020-04-23T19:07:37Z

I have pushed the changes to my master branch. ~~The bug report and feature request templates are not showing up, but I think that is because my repo is a fork:~~ EDIT: I fixed it.

Try it out here: https://github.com/FranciscoPombal/qBittorrent/issues/new/choose

Here is what it looks like for a user:

Note that the headers in the files like the following are metadata for github only and do not show up when the user is creating the issue:

---
name: Feature Request
about: Suggest a new feature or enhancement for qBittorrent.
title: ''
labels: 'Feature request'
assignees: ''
---

As a bonus, feature requests get automatically labeled on creation.

xavier2k6 · 2020-11-08T12:46:02Z

<!--
###############################################################################
WARNING!
IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN THE ISSUE BEING CLOSED
AS INCOMPLETE/INVALID
DO NOT DELETE HEADINGS/SECTIONS (LEAVE BLANK IF NOT APPLICABLE)
###############################################################################
Please make sure the description is worded/structured well enough to be understood.
Provide steps to reproduce the issue.
Provide as much context/additional relevant information/examples as possible.
Suggested solution (if applicable).
Do not forget about the mandatory attachments!.

For more information consult the Contributing Guidelines at https://github.com/qbittorrent/qBittorrent/blob/master/CONTRIBUTING.md.
################################## IMPORTANT ###################################
Type your text under the HEADINGS/SECTIONS below (LEAVE BLANK IF NOT APPLICABLE)
Use the Preview tab before posting to ensure correct formatting.
###############################################################################
-->
#### qBittorrent version/architecture (32bit/64bit)

#### Operating system/version

#### (If on windows), please include (FULL version displayed in `command prompt` window) e.g. `[Version 10.0.19042.xyz]`

#### (If on Linux), please include `libtorrent-rasterbar` and `Qt` version

#### Install method (Official installer/Self-compiled/Other - please specify)

#### What is the problem

#### What is the expected behavior

#### Detailed steps to reproduce the problem

#### Extra info (if any)

#### Mandatory Attachments (log(s) and settings file)

How about something like this??
Big wall of text to go through currently in this PR (that I can see people - straight away, deleting & writing their own thing.)
I know, I certainly don't like it!!

Result:

qBittorrent version/architecture (32bit/64bit)

Operating system/version

(If on windows), please include (FULL version displayed in `command prompt` window) e.g. `[Version 10.0.19042.xyz]`

(If on Linux), please include `libtorrent-rasterbar` and `Qt` version

Install method (Official installer/Self-compiled/Other - please specify)

What is the problem

What is the expected behavior

Detailed steps to reproduce the problem

Extra info (if any)

Mandatory Attachments (log(s) and settings file)

xavier2k6 · 2020-11-08T12:47:05Z

The reason I included the FULL Version string is that:
It gives a more searchable text string for determining what OS the qBittorrent user base runs,
This will also aid in the raising "Minimum Supported"/"Dropping" of EOL OS's/because of dependencies/compilers etc.

For example:

Windows 11

Windows 11 (22H2 / 10.0.22621) - {EOL - Oct 14th, 2024}
Windows 11 (21H2 / 10.0.22000) - {EOL - Oct 10th, 2023}

Windows 10

Windows 10 (22H2 / 10.0.19045) - {EOL - Oct 14th, 2025}
Windows 10 (21H2 / 10.0.19044) - {EOL - Jun 13th, 2023}
Windows 10 (21H1 / 10.0.19043) - {EOL - Dec 13th, 2022}
Windows 10 (20H2 / 10.0.19042) - {EOL - May 10th, 2022}
Windows 10 (2004 (20H1) / 10.0.19041) - {EOL - Dec 14th, 2021}
Windows 10 (1909 (19H2) / 10.0.18363) - {EOL - May 11th, 2021}
Windows 10 (1903 (19H1) / 10.0.18362) - {EOL - Dec 8th, 2020}
Windows 10 (1809 / 10.0.17763) - {EOL - Nov 10th, 2020}
Windows 10 (1803 / 10.0.17134) - {EOL - Nov 12th, 2019}
Windows 10 (1709 / 10.0.16299) - {EOL - Apr 9th, 2019}
Windows 10 (1703 / 10.0.15063) - {EOL - Oct 9th, 2018}
Windows 10 (1607 / 10.0.14393) - {EOL - Apr 10th, 2018}
Windows 10 (1511 / 10.0.10586) - {EOL - Oct 10th, 2017}
Windows 10 (1507 / 10.0.10240) - {EOL - May 9th, 2017}

Windows 7 / 8 / 8.1

Windows 8.1 (6.3.9600) - {EOL - Jan 10, 2023)}
Windows 8 (6.2.9200) - (EOL- Jan 12, 2016)
Windows 7 SP1 (6.1.7601) - {EOL - Jan 14, 2020}
Windows 7 (6.1.7600) - {EOL - Jan 14, 2020}

Windows Operating Systems no longer supported as of 4.2.0 Release (December 3rd 2019)

Windows XP / Vista

Windows Vista SP2 (6.0.6002) - {EOL - Apr 11, 2017}
Windows Vista SP1 (6.0.6001) - {EOL - Apr 11, 2017}
Windows Vista (6.0.6000) - {EOL - Apr 11, 2017}
Windows XP (5.1.2600) - {EOL - April 8, 2014}

xavier2k6 · 2020-11-08T14:30:03Z

#### qBittorrent version/architecture (32bit/64bit)
<!--Type your text after the `>` to the right-->
#### Operating system/version
<!--Type your text after the `>` to the right-->
#### (If on windows), please include (FULL version displayed in `command prompt` window) e.g. `[Version 10.0.19042.xyz]`
<!--Type your text after the `>` to the right-->
#### (If on Linux), please include `libtorrent-rasterbar` and `Qt` version
<!--Type your text after the `>` to the right-->
#### Install method (Official installer/Self-compiled/Other - please specify)
<!--Type your text after the `>` to the right-->
#### What is the problem
<!--Type your text after the `>` to the right-->
#### What is the expected behavior
<!--Type your text after the `>` to the right-->
#### Detailed steps to reproduce the problem
<!--Type your text after the `>` to the right-->
#### Extra info (if any)
<!--Type your text after the `>` to the right-->
#### Mandatory Attachments (log(s) and settings file)
<!--Paste links/Drop the files on next line below this statement.-->

Or maybe this?

RESULT:

qBittorrent version/architecture (32bit/64bit)

Operating system/version

(If on windows), please include (FULL version displayed in `command prompt` window) e.g. `[Version 10.0.19042.xyz]`

(If on Linux), please include `libtorrent-rasterbar` and `Qt` version

Install method (Official installer/Self-compiled/Other - please specify)

What is the problem

What is the expected behavior

Detailed steps to reproduce the problem

Extra info (if any)

Mandatory Attachments (log(s) and settings file)

FranciscoPombal · 2020-11-08T19:38:31Z

Big wall of text to go through currently in this PR (that I can see people - straight away, deleting & writing their own thing.)

Then their issue will be immediately closed and locked as invalid. This is a feature, not a bug, to filter out users who are not willing to put in the minimum effort.

xavier2k6 · 2020-11-08T20:00:58Z

Then their issue will be immediately closed and locked as invalid. This is a feature, not a bug, to filter out users who are not willing to put in the minimum effort.

You have to take in to account that for some users - looking at that wall of text is basically double dutch & may know nothing about markdown etc so may not know how it's supposed to look etc.

There have been users here, who have made issues & just pasted the SIGABRT crash reports for example with remarks like.....I dunno, just happened....it told me to report it here, so I did. (deleted - the template etc)

OpenSSL/Libtorrent/Boost don't even have that kind of text to read through/fiddle with etc.

Keep it to bare minimum/essentials & it's followed up.

xavier2k6 · 2020-11-08T20:06:53Z

This is OpenSSL's

<!--
Thank you for your bug report. If this is your first one,
please take the time to read the following lines before posting it.

NOTE:

    If you're asking about how to use OpenSSL, this isn't the right 
    forum.  Please see our User Support resources:
    https://github.com/openssl/openssl/blob/master/.github/SUPPORT.md

Please remember to tell us in what OpenSSL version you found the issue.

For build issues:

    If this is a build issue, please include the configuration output
    as well as a log of all errors.  Don't forget to include the exact
    commands you typed.

    With OpenSSL before 1.1.1, the configuration output comes from the
    configuration command.  With OpenSSL 1.1.1 and on, it's the output
    of `perl configdata.pm --dump`

For other issues:

    If it isn't a build issue, example code or commands to reproduce
    the issue is highly appreciated.
    Also, please remember to tell us if you worked with your own
    OpenSSL build or if it is system provided.

Please remember to put ``` lines before and after any commands plus
output and code, like this:

    ```
    $ echo output output output
    output output output
    ```

    ```
    #include <stdio.h>
    
    int main() {
        int foo = 1;
        printf("%d\n", foo);
    }
    ```
-->

FranciscoPombal · 2021-06-03T00:04:24Z

@xavier2k6

Suggest -> issue reporting section

Suggest -> feature request section

👍, done.

Suggest -> Changing All headers to something like below to avoid seeing (type here)

### qBittorrent info and operating system(s) 

### If on Linux, libtorrent-rasterbarandQt versions 

I understand but I disagree (I have also thought of this in the past). I'm always concerned users will write inside the , which is worse than leaving a (type here).

We already explicitly warn the user to delete each (type here) as they fill out the template in a comment above.
I think it's better to go with (type here) for now, if we still see that many users are not deleting the (type here)s, we can then try alternative solutions such as the one you propose.

Chocobo1 · 2021-06-03T02:17:21Z

@Chocobo1, do you have any blocking objections?

no.

xavier2k6 · 2021-06-03T09:07:48Z

I understand but I disagree (I have also thought of this in the past). I'm always concerned users will write inside the , which is worse than leaving a (type here).

Well, if they do that & we are attempting to tighten up the issue tracker procedures in this PR then we can mark it as invalid can't we? (as they didn't follow our instructions correctly)

One overall checkbox may be sufficient enough for compliance with the instructions set out in markdown text but I won't insist on this.

My opinion from #12574 (comment) would still be the best option & as I said previously this is something that should be looked at in the future. (Maybe 6 months from now?)

I don't think I have any other issues with this PR.

FranciscoPombal · 2021-06-03T09:39:56Z

@xavier2k6

Well, if they do that & we are attempting to tighten up the issue tracker procedures in this PR then we can mark it as invalid can't we? (as they didn't follow our instructions correctly)

Well we should be strict, but not super strict in closing issues for being invalid. A user may make an honest mistake; with the  approach, the issue may not be understandable unless we specifically inspect the raw text. With the (type here) approach, the most that can happen in that case is that there is an extra (type here) appended/prepended to whatever the user writes, which is not ideal, but not that harmless, as the content is still all readable - and not a reason alone to close the report.

One overall checkbox may be sufficient enough for compliance with the instructions set out in markdown text but I won't insist on this.

We can always change this in the future if users complain about it. Fortunately I doubt this will be the case. As I've demonstrated before, multiple other projects have been using the "multiple checkbox" method successfully for a long time. They keep the user engaged and alert as they are reading and fulfilling each requirement.

My opinion from #12574 (comment) would still be the best option & as I said previously this is something that should be looked at in the future. (Maybe 6 months from now?)

First we should see how this one does "in production". This might not be the perfect solution until the end of time, but it sure has a much better chance of being more effective than what we have now, and it is proven in other even bigger projects.

Then sure, something based on google forms can be looked at in the future. However, I have expressed my reservations about it, and I'd like to add that some users might not like the fact that they have to interact with an external Google resource just to submit an issue...

I don't think I have any other issues with this PR.

👍

FranciscoPombal · 2021-06-03T09:48:15Z

@glassez @Chocobo1

@Chocobo1, do you have any blocking objections?

no.

Cool, can we finally get this approved and merged then? I believe @xavier2k6 and @thalieht 's concerns have been addressed (but let me know if there is still some last minute change that you need!).

glassez

Cosmetic comment: file names inside ISSUE_TEMPLATE seem to be inconsistent to me (namely using of _template suffix).
Also why some *.md files have UPPERCASE names but others not? Is there any general naming scheme/convention?

FranciscoPombal · 2021-06-04T10:17:40Z

@glassez

Cosmetic comment: file names inside ISSUE_TEMPLATE seem to be inconsistent to me (namely using of _template suffix).
Also why some *.md files have UPPERCASE names but others not? Is there any general naming scheme/convention?

I followed the conventions/guidelines in GitHub's documentation.

Basically,

.github/ISSUE_TEMPLATE directory name must be upper case
.github/PULL_REQUEST_TEMPLATE directory name must be upper case
the name of the files inside .github/{ISSUE, PULL_REQUEST}_TEMPLATE are case-insensitive. So I chose lower case, to follow the convention of the rest of the files in the repository that don't have a case-sensitivity requirement.
SUPPORT.md must (should?) be named exactly like that
FUNDING.yml must (should?) be named exactly like that

References:

The .github/PULL_REQUEST_TEMPLATE/pull_request_template.md file name should not contain the _template suffix for consistency with the rest, you are right about that, will push shortly to fix it.

- Separate templates into bug report and feature request - Add a checklist and guidance comments - Add a PR template - Add SUPPORT.md

FranciscoPombal · 2021-06-07T15:34:11Z

@glassez @Chocobo1 macOS CI failure is obviously spurious.

glassez · 2021-06-08T17:48:39Z

Thank you!

ArcticGems · 2021-06-08T19:26:21Z

Maybe when it's time to release 4.4.0 beta, you guys can add another part called something like "[4.4.0 Beta] Bug report" with its own checklist and relevant questions?

FranciscoPombal · 2021-06-09T10:38:51Z

Maybe when it's time to release 4.4.0 beta, you guys can add another part called something like "[4.4.0 Beta] Bug report" with its own checklist and relevant questions?

These templates can be used without changes for such purposes. It is sufficient for the user to write "4.4.0 Beta" in the version field. If we really do need a clearer separation between issues from that version and others, we'll just label them differently as they're posted.

thalieht · 2021-08-10T23:58:42Z

.github/ISSUE_TEMPLATE/bug_report.md

+-->
+
+- qBittorrent version: (type here)
+- Operating system(s) where the issue occurs: (type here)


After reading a few issues, these "qBittorrent version:" and "Operating system(s) where the issue occurs:" are disrupting the flow of reading. I can't easily filter them to get to the juicy part and furthermore i think they are unnecessary. A simple "(type here)" is sufficient IMO.
Same goes for the section below.

ArcticGems · 2021-08-14T11:51:42Z

I think the 'bug report form' that you can find in the 'uBlock-issues' repository is interesting. No more template evading/removing or checkbox mistakes!

It's worth looking into.

PR: uBlockOrigin/uBlock-issues#1651

Check out how it looks here (start a issue, but don't submit) =
https://github.com/uBlockOrigin/uBlock-issues/issues

xavier2k6 · 2021-08-14T16:05:37Z

@ArcticGems Thank you so much!!!

@glassez this is a very useable option like what I had similarly suggested in #12574 (comment)

https://github.com/uBlockOrigin/uBlock-issues/blob/master/.github/ISSUE_TEMPLATE/bug_report.yml

https://github.com/uBlockOrigin/uBlock-issues/blob/master/.github/ISSUE_TEMPLATE/config.yml

I'll try to work on this/submit PR over the wknd.

xavier2k6 · 2021-08-14T22:09:41Z

Here's an example:

FranciscoPombal added the Project management label Apr 21, 2020

FranciscoPombal requested review from sledgehammer999, glassez, thalieht and Chocobo1 April 21, 2020 18:38

FranciscoPombal mentioned this pull request Apr 21, 2020

Revise contributing guidelines #11896

Closed

NotTsunami suggested changes Apr 22, 2020

View reviewed changes

.github/ISSUE_TEMPLATE.md Outdated Show resolved Hide resolved

.github/ISSUE_TEMPLATE.md Outdated Show resolved Hide resolved

.github/ISSUE_TEMPLATE.md Outdated Show resolved Hide resolved

Chocobo1 removed their request for review April 22, 2020 07:15

FranciscoPombal force-pushed the contrib-it branch from cd2f51c to b4e1015 Compare April 22, 2020 10:24

LordNyriox reviewed Apr 23, 2020

View reviewed changes

.github/ISSUE_TEMPLATE.md Outdated Show resolved Hide resolved

FranciscoPombal force-pushed the contrib-it branch from b4e1015 to 83d80cf Compare April 23, 2020 18:44

FranciscoPombal force-pushed the contrib-it branch from 83d80cf to 893dff8 Compare April 23, 2020 18:51

FranciscoPombal changed the title ~~Revise ISSUE_TEMPLATE.md~~ Revise GitHub templates Apr 23, 2020

FranciscoPombal mentioned this pull request Apr 28, 2020

[Tool] Batch close old issues #12679

Closed

FranciscoPombal force-pushed the contrib-it branch 2 times, most recently from 75aa23d to c901ec0 Compare April 28, 2020 17:16

FranciscoPombal force-pushed the contrib-it branch from c901ec0 to f2b43fa Compare May 6, 2020 09:33

FranciscoPombal mentioned this pull request Sep 13, 2020

Issue management #11161

Closed

FranciscoPombal force-pushed the contrib-it branch from f2b43fa to 329caf8 Compare September 21, 2020 17:40

FranciscoPombal force-pushed the contrib-it branch from 912af34 to 543ea63 Compare June 2, 2021 23:58

xavier2k6 previously approved these changes Jun 3, 2021

View reviewed changes

glassez reviewed Jun 4, 2021

View reviewed changes

Revise GitHub templates

437769a

- Separate templates into bug report and feature request - Add a checklist and guidance comments - Add a PR template - Add SUPPORT.md

FranciscoPombal dismissed xavier2k6’s stale review via 437769a June 4, 2021 10:19

FranciscoPombal force-pushed the contrib-it branch from 543ea63 to 437769a Compare June 4, 2021 10:19

FranciscoPombal requested review from xavier2k6 and glassez June 4, 2021 10:19

glassez approved these changes Jun 4, 2021

View reviewed changes

xavier2k6 approved these changes Jun 4, 2021

View reviewed changes

Chocobo1 approved these changes Jun 7, 2021

View reviewed changes

glassez merged commit 9f03598 into qbittorrent:master Jun 8, 2021

FranciscoPombal deleted the contrib-it branch June 8, 2021 18:01

thalieht reviewed Aug 10, 2021

View reviewed changes

This comment has been minimized.

Sign in to view

xavier2k6 mentioned this pull request Aug 16, 2021

Replace GitHub markdown templates with GitHub forms #15330

Merged

xavier2k6 mentioned this pull request Oct 17, 2023

Improve NSIS scripts #19728

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Revise GitHub templates #12574

Revise GitHub templates #12574

FranciscoPombal commented Apr 21, 2020 •

edited

Loading

xavier2k6 commented Apr 21, 2020

FranciscoPombal commented Apr 22, 2020

LordNyriox commented Apr 23, 2020

FranciscoPombal commented Apr 23, 2020 •

edited

Loading

FranciscoPombal commented Apr 23, 2020 •

edited

Loading

xavier2k6 commented Nov 8, 2020 •

edited

Loading

xavier2k6 commented Nov 8, 2020 •

edited

Loading

xavier2k6 commented Nov 8, 2020 •

edited

Loading

FranciscoPombal commented Nov 8, 2020

xavier2k6 commented Nov 8, 2020

xavier2k6 commented Nov 8, 2020

FranciscoPombal commented Jun 3, 2021

Chocobo1 commented Jun 3, 2021

xavier2k6 commented Jun 3, 2021

FranciscoPombal commented Jun 3, 2021 •

edited

Loading

FranciscoPombal commented Jun 3, 2021

glassez left a comment •

edited

Loading

FranciscoPombal commented Jun 4, 2021

FranciscoPombal commented Jun 7, 2021

glassez commented Jun 8, 2021

ArcticGems commented Jun 8, 2021

FranciscoPombal commented Jun 9, 2021

thalieht Aug 10, 2021

ArcticGems commented Aug 14, 2021

xavier2k6 commented Aug 14, 2021 •

edited

Loading

xavier2k6 commented Aug 14, 2021

This comment has been minimized.

Revise GitHub templates #12574

Revise GitHub templates #12574

Conversation

FranciscoPombal commented Apr 21, 2020 • edited Loading

xavier2k6 commented Apr 21, 2020

FranciscoPombal commented Apr 22, 2020

LordNyriox commented Apr 23, 2020

FranciscoPombal commented Apr 23, 2020 • edited Loading

FranciscoPombal commented Apr 23, 2020 • edited Loading

xavier2k6 commented Nov 8, 2020 • edited Loading

Result:

qBittorrent version/architecture (32bit/64bit)

Operating system/version

(If on windows), please include (FULL version displayed in command prompt window) e.g. [Version 10.0.19042.xyz]

(If on Linux), please include libtorrent-rasterbar and Qt version

Install method (Official installer/Self-compiled/Other - please specify)

What is the problem

What is the expected behavior

Detailed steps to reproduce the problem

Extra info (if any)

Mandatory Attachments (log(s) and settings file)

xavier2k6 commented Nov 8, 2020 • edited Loading

For example:

Windows 11

Windows 10

Windows 7 / 8 / 8.1

Windows Operating Systems no longer supported as of 4.2.0 Release (December 3rd 2019)

Windows XP / Vista

xavier2k6 commented Nov 8, 2020 • edited Loading

RESULT:

qBittorrent version/architecture (32bit/64bit)

Operating system/version

(If on windows), please include (FULL version displayed in command prompt window) e.g. [Version 10.0.19042.xyz]

(If on Linux), please include libtorrent-rasterbar and Qt version

Install method (Official installer/Self-compiled/Other - please specify)

What is the problem

What is the expected behavior

Detailed steps to reproduce the problem

Extra info (if any)

Mandatory Attachments (log(s) and settings file)

FranciscoPombal commented Nov 8, 2020

xavier2k6 commented Nov 8, 2020

xavier2k6 commented Nov 8, 2020

FranciscoPombal commented Jun 3, 2021

Chocobo1 commented Jun 3, 2021

xavier2k6 commented Jun 3, 2021

FranciscoPombal commented Jun 3, 2021 • edited Loading

FranciscoPombal commented Jun 3, 2021

glassez left a comment • edited Loading

Choose a reason for hiding this comment

FranciscoPombal commented Jun 4, 2021

FranciscoPombal commented Jun 7, 2021

glassez commented Jun 8, 2021

ArcticGems commented Jun 8, 2021

FranciscoPombal commented Jun 9, 2021

thalieht Aug 10, 2021

Choose a reason for hiding this comment

ArcticGems commented Aug 14, 2021

xavier2k6 commented Aug 14, 2021 • edited Loading

xavier2k6 commented Aug 14, 2021

This comment has been minimized.

FranciscoPombal commented Apr 21, 2020 •

edited

Loading

FranciscoPombal commented Apr 23, 2020 •

edited

Loading

FranciscoPombal commented Apr 23, 2020 •

edited

Loading

xavier2k6 commented Nov 8, 2020 •

edited

Loading

(If on windows), please include (FULL version displayed in `command prompt` window) e.g. `[Version 10.0.19042.xyz]`

(If on Linux), please include `libtorrent-rasterbar` and `Qt` version

xavier2k6 commented Nov 8, 2020 •

edited

Loading

xavier2k6 commented Nov 8, 2020 •

edited

Loading

(If on windows), please include (FULL version displayed in `command prompt` window) e.g. `[Version 10.0.19042.xyz]`

(If on Linux), please include `libtorrent-rasterbar` and `Qt` version

FranciscoPombal commented Jun 3, 2021 •

edited

Loading

glassez left a comment •

edited

Loading

xavier2k6 commented Aug 14, 2021 •

edited

Loading