Author Topic: Sourceforge Ticket review - feeback on easy tickets to close part 1  (Read 4378 times)

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
I have been looking at the open sourceforge tickets as there currently 496 open tickets, which is allot. A bunch of them are low hanging in that they can be closed with the following:
a)  Read the posts in the ticket and based on the post the ticket can be closed.
b) Testing with the latest nightly or recent Linux nightly versions do not exhibit the issue/bug/feature request is included in the nightly.
c) No enough info to reproduce the bug and the ticket is from 2016.
d) Bug or issue has not been seen or cannot be reproduced and the original poster has been asked to try a later version or supply more into and no response from years ago has been posted.
e) The ticket is a duplicate where I could easily find that it is a duplicate.

I have looked a at the 251 tickets so far and found the following:
- 99 Can be closed without any coding and minimal testing or reading etc a per the list above
- 28 Can be closed, but need to be looked at by one of the main CB developers to see if the ticket is okay to close.
- 94 are open
- 30 need a bit of time spent on them to see if the patch or fix in the ticket is okay or not and then get the patch applied. Some will be bad and some will be okay an others will need allot of work.

Please find in the attached (in the zip as xlsx cannot be attached) excel spread hseet the 99 that I think can be closed. I have put my comments in column C and my proposed status in column d, otherwise the data is from sourceforge (unless something has gone wrong).

Is there anyone who can take the list and run with it, so that the open sourceforge tickets can be reduced?

In the mean time I will keep looking at the rest of the tickets, but I expect that the number of easy tickets that can be closed will be less as they are more recent tickets.


Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13438
    • Travis build status
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #1 on: June 24, 2021, 09:29:14 am »
Is there anyone who can take the list and run with it, so that the open sourceforge tickets can be reduced?
I cannot because xlsx is not a file type I can open... Try simple text files :)

And the actual problem is not that there are too many tickets, but there are too few people able/willing to solve them.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #2 on: June 24, 2021, 09:39:38 am »
Do you have Libreoffice installed? If not I will upload a CSV.

That is why I chose to only give the list of tickets that are IMHO easy to close and not the ones that will take say 15+ minutes to look at. I think there may be a few 1 - 3 in the list where the info is in a thread that may take 5 to 10 minutes to read, but no code changes are required from the thread posts.
« Last Edit: June 24, 2021, 09:43:17 am by AndrewCot »

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #3 on: June 24, 2021, 09:56:05 am »
In the attached zip are the following files, which at worst you can use the Poposed_CB_Tickets_24JUN2021_Close_Only_Comments.csv file:
Poposed_CB_Tickets_24JUN2021_Close_Only.ods
Poposed_CB_Tickets_24JUN2021_Close_Only.xlsx
Poposed_CB_Tickets_24JUN2021_Close_Only_Comments.csv
Poposed_CB_Tickets_24JUN2021_Close_Only_Full.csv

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3006
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #4 on: June 24, 2021, 09:51:50 pm »
Thank you for your work..

and i agree on some tickets and will work the list on closing some.

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #5 on: June 25, 2021, 05:09:53 am »
No worries.

BTW I have reached out to the fortran plugin devs on their google discussion group board (https://groups.google.com/g/cbfortran) to look at the Fortran tickets once I get a list of tickets for them to look at and they were okay with this. I think any future tickets related to fortran should probably be posted to the google cb fortran board to look at as they will be way better at looking into it than any C++ dev.



Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #6 on: June 25, 2021, 11:43:36 am »
I am starting to see a few wxSmith bugs. Is there someone that I should ask to see if they are relevant or not etc? If there is not someone then I will leave them as open as I do not want to spend allot of time on them at the moment as I do not use CB for wxwidget GUI apps.

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #7 on: June 27, 2021, 01:30:59 am »
    I have completed my first pass of the tickets and my proposed results are for the 497 currently open are:
    • 163 should be easy to close with no work, apart from reading the ticket and/or forum posts.
    • 190 still open - these need work
    • 171 to be looked at on the second pass to see if the current proposal can be refined or needs to change.

    I am seeing a few patterns as follows:
    • - There are a bunch of tickets for the following:
      • Fortran - asked fortran plugin owner to look at them.
      • wxsmith - seems to be an area that has issues.
      • Visual studio support - current support is very old.
      • Compiler auto detection on Windows or windows compiler setup and/or configure issues .
    • Some tickets have patches, but there is no feedback on the patch and that patch was not applied to the trunk.
    • Ticket fixes were started but not completed by various devs.
    • Ticket fixes were started and there were differing opinions on how it should be done, which is good for a healthy project, BUT then it went no where. Even worse was that some of the workwas okay and this never even made it into the trunk.


     

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #8 on: June 27, 2021, 05:14:41 am »
Please find in the attached zip file the following updated files that now include all of the current tickets that should be able to be closed easily with no work:

  • CodeBlocks_Tickets_27JUN2021_Proposed_Close_Only.csv
  • CodeBlocks_Tickets_27JUN2021_Proposed_Close_Only.ods
  • CodeBlocks_Tickets_27JUN2021_Proposed_Close_Only.xlsx
  • CodeBlocks_Tickets_27JUN2021_Proposed_Close_Only_Comments.csv

If who ever eventually takes this an runs with does not agree with a ticket to be closed please keep track of them in a spreadsheet or csv or text file so at the end you have a list that cannot be closed for some reason so it can be discussed.

Currently my breakdown of the open tickets into some sort of category with counts currently is:

Row Labels   Count
Check & test   3
Check/ Test / Apply change   1
Close   170
close?   19
open   193
TBA   12
Test / Apply change   46
Not Checked   9
open - VisualStudio   2
Fortran -Not Checked   2
Fortran -open   3
open - wxsmith   6
Fortran - TBA   1
Reproduce   10
Waiting for response   17
Open - non ascii   2
Close - Duplicate   1
Grand Total   497



Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5380
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #9 on: June 28, 2021, 09:41:47 am »
Please find in the attached zip file the following updated files that now include all of the current tickets that should be able to be closed easily with no work:
...

You forgot uploading the attachment?

Thanks for your contribution!
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline AndrewCot

  • Almost regular
  • **
  • Posts: 182
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #10 on: June 28, 2021, 09:54:15 am »
Try now for attachment.