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

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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: 3263
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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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: 5720
  • 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

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
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.

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1201
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #11 on: May 12, 2022, 09:11:19 am »
This is the same file up to current date, in ODS and XLS formats.

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #12 on: May 12, 2022, 12:14:32 pm »
Do you want a list of what I think should be very easy to close tickets? These will ones I think can be closed based on the info in the ticket and are very low hanging.

Attached is my latest spreadsheet, but this time I have moved tickets related to the following into a their own worksheet (okay the ones I spotted, so if you find ones I have not moved please let me know):
  • Mac / OSX   (16 tickets)
  • MS Visual Studio   (5 tickets)
  • Code Completion  (55 tickets)

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #13 on: May 12, 2022, 01:02:21 pm »
This is the list of tickets that should be easy to close based on the info in the tickets.
#|Summary▾|Comment
1078|Log display auto scrolls to top sometimes after compiling|Close as per last post in the ticket.
1040|codeblocks.org cert is invalid|Cert is a Cloudflare Inc ECC CA-3 one. As such this ticket can be closed.
970|32-bit Win7 - gcc Not Compatible With Version of Windows Running|Original 20.03 mingw included mingw64 and looks to be fixed on 29-Dec-2020, but no announcemnets were done.
952|20.04: copy/​paste problem on Ubuntu|Close as per last post.
901|Search -> Replace fails when there are multiple selections|Ticket includes inappropriaye posts from creator. Not checked. Close due to inappropriate posts. Very low priority issue which will not get fixed.
825|Add progress dialog to workspace/​project loading|Clsoe, see ticket 833.
803|Edit PGI FORTRAN Win32 static link command|No lonerg applicable as per last ticket post. As such this ticket can be closed.
622|Static Libraries not rebuilt if Static Library dependency is rebuilt|Close, see post from Teodor in ticket. As such this ticket can be closed.
482|Code::Blocks freezing |Initial issue with Windows, which seems to be resolved as I have not had CB crash randomly without a reason sicne 20.03. The report form 2020 is fro a chromebook machine. As such this was probably a wxwidget issue from 2016 and there this ticket can be closed.
432|editor: find word under cursor|Wx2.8 bug, fixed in 3.0 as it works okay with 3.x as per last post this bug can be closed.
403|bug in creating file folder of codeblocks 16.01 (windows 10) |Working okay on SVN-12462 and bluehazzard could also not reproduce. As such the ticket can be closed.
366|No Symbols and Code folding problem|Working okay on SVN-12462, so close the ticket.
320|"make" from the released 16.01 version tries to run autotools|Unix/Linux build issue related to 16.01 assuming it's a dev environment config issue and as such it can be closed as it is 5 years old.
287|Occasional Assert in wxDebugReport::AddContext|Have not seen this, so assuming it has been fixed in release after ticket was reported.
273|F2 (logs window) not correcly working inside Editor|Works okay on Linux Mint 20.1 with CB SVN12286 wxWidget 3.0.4.
187|Need option to select indent format within switch statements|CB astyle plugin was changed in 2015 to add options to resolve this ticket. Works in SVN r12458
167|OS bricked by breakpoints|This is resolved. I cannot say why, but I have debugged later versions of the code on Ubuntu 18, 20 & Win10 with CB and CB works. The app does not always play ball when you stop a thread and does occasionally crash the OS due to bugs in the app.
115|"Copy contents to clipboard" right-click menu gives incorrect line endings|Agree cannot fix, so close

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1201
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #14 on: May 12, 2022, 05:20:55 pm »
115, 187, 432, 901, 952 and 1078 closed... Can you striketrough them in your message?

366 is owned by ollydbg

« Last Edit: May 12, 2022, 06:43:43 pm by Miguel Gimenez »

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1201
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #15 on: May 13, 2022, 04:56:47 pm »
320 and 970 closed...

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #16 on: September 22, 2022, 06:35:04 am »
Below is a list of tickets which have the owner set:

1277    |    bluehazzard    |    Add UI to store default values and descriptions of global variables in project files
1262    |    bluehazzard    |    Status bar
1261    |    bluehazzard    |    Add button to switch between Intel and AT&T disassembly style in the disassembly window
1260    |    bluehazzard    |    Bring codeblocks plugin wizard up to date
1258    |    bluehazzard    |    Thread Search context/CollapseAll in ListSTC Type
1255    |    bluehazzard    |    Gray out file not build/link by the currently selected target
1056    |    bluehazzard    |    "Objects output dir" field is silently deleted
960    |    bluehazzard    |    SFML Project Template Wizard
900    |    bluehazzard    |    Update for plugin script
854    |    bluehazzard    |    Batch build stalls when window is not active
851    |    bluehazzard    |    Show length of selected text
832    |    bluehazzard    |    wxSmith does not honor CR-LF mode
806    |    bluehazzard    |    [class wizard] Add more styling options to class wizard
797    |    bluehazzard    |    [ThreadSearch] The drop down boxes for mask and dirs is not set in the option dialogs
789    |    bluehazzard    |    [wxSmith] Sizer and wxAUI bugs
778    |    bluehazzard    |    Sorting the output of the Vera++/cppchecker
729    |    bluehazzard    |    Add UI for project globs
617    |    bluehazzard    |    [wxSmithSTC] Replace wxScintilla with wxStyledTextCtrl and fix multiple other errors
511    |    bluehazzard    |    [ScriptedWizard] Add button for global vars in "Generic select path" dialog
461    |    bluehazzard    |    Switch to the next file in the stack when the ctrl-tab/ctrl-, button is pressed
48    |    bluehazzard    |    Print dialogue appears for every file when batch printing multiple files
246    |    Jens Lody    |    Project loading/layout speedup
163    |    Jens Lody    |    Put a copy of wxwin.m4 inside m4/
1030    |    Lieven de Cock    |    Entry Point not Found on Windows XP
1188    |    Morten MacFly    |    Macromanager does not replace double qote macro with nothing in the expansion
1184    |    Morten MacFly    |    Add ability to save and export and import the global variables in the global vaiiable editor
1126    |    Morten MacFly    |    When loading a project no compiler validation checks are done
1119    |    Morten MacFly    |    Windows Installer update request
868    |    Morten MacFly    |    Project Options Manipulator plugin
270    |    Morten MacFly    |    Projects do not build when swapping source files.
128    |    Morten MacFly    |    Changing compilers leaves old options laying around
99    |    Morten MacFly    |    ThreadSearch and Lib Finder plugins depend on wxSmith plugin (windows installer problem)
5    |    Morten MacFly    |    Support Visual Studio 2012
1045    |    ollydbg    |    plugin / contrib / help / unreachable code
286    |    ollydbg    |    CC crash when closing workspace
281    |    ollydbg    |    Let's CC support Conditional Code :: Blocks. highlighting in the editor
239    |    ollydbg    |    Windows: use only one pch file for all targets, also reduce exported symbols from codeblocks.dll
224    |    ollydbg    |    Duplication in documentation tooltip
177    |    ollydbg    |    Code completion fails with enum variables defined/declared along with the enum types
158    |    ollydbg    |    Code completion fails with the "using Alias = Type" syntax in C++11
145    |    ollydbg    |    Code completion ignores parameters of catch-clauses
127    |    ollydbg    |    Code completion fails with complex declarations/definitions
47    |    ollydbg    |    Show call tip of the constructor function
31    |    ollydbg    |    restrict keyword and auto-completion
959    |    Teodor Petrov    |    Editor: code folding bar artefacts in HiDPI
946    |    Teodor Petrov    |    Retina support for wxSmith
943    |    Teodor Petrov    |    Use system hotlight color for start page links
928    |    Teodor Petrov    |    SmartIndent doesn't add closing brackets properly
922    |    Teodor Petrov    |    Debugger breakpoints with invalid fullname path
783    |    Teodor Petrov    |    Folding: "Fold all on open" performs 'Toggle All', instead of 'Fold All'
776    |    Teodor Petrov    |    File permissions changed when saved on Windows
638    |    Teodor Petrov    |    debuggergdb: add pipe remote debugging protocol
587    |    Teodor Petrov    |    Add theme support for Settings->Environment->Colours
575    |    Teodor Petrov    |    The editormanager does not close all open tabs with deleted files
442    |    Teodor Petrov    |    Extend macro expansion
411    |    Teodor Petrov    |    CB becomes unusable if the project is modified when build options is open on Linux
404    |    Teodor Petrov    |    Ctrl+Tab moves focus instead of switching editor tabs
395    |    Teodor Petrov    |    Add UTIs to the OS X plist
341    |    Teodor Petrov    |    Some additions to scriptwizard bindings
329    |    Teodor Petrov    |    Debuger bug
325    |    Teodor Petrov    |    Speedup opening of "Goto file..." dialog in large projects
317    |    Teodor Petrov    |    Discriminating files with the same name
305    |    Teodor Petrov    |    Assert failure: invalid encoding value in wxCSConv ctor
283    |    Teodor Petrov    |    Bug e Outros 15.xx Brasil C++ Previs Erros
250    |    Teodor Petrov    |    Proposal - debugger perspective defaults, additional debugger windows
209    |    Teodor Petrov    |    Bug in debugger logic
184    |    Teodor Petrov    |    Excessive X traffic in response to key press in editor window
174    |    Teodor Petrov    |    Breakpoints removed from editor are not removed from GDB
169    |    Teodor Petrov    |    Predefined user commands for debugger plugin
138    |    Teodor Petrov    |    GDB showing return value
132    |    Teodor Petrov    |    Feature request: Make Backup Directory Configuranble
120    |    Teodor Petrov    |    folding causes incorrect display, occasionally lines of code vanish
60    |    Teodor Petrov    |    Enable file delete from file context menu in project window
49    |    Teodor Petrov    |    Add flag to exclude some project files from search
44    |    Teodor Petrov    |    Code completion when typing in multiple selections simultaneously
1074    |    Yiannis Mandravellos    |    Codeblocks Forum links Broke

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1201
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #17 on: September 22, 2022, 04:33:00 pm »
You can delete 575.

Tickets owned by Teodor Petrov are orphans now.

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #18 on: September 23, 2022, 09:39:33 am »
Should someone change the tickets to remove the owner where it is set to Teodor Petrov?

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #19 on: September 23, 2022, 09:41:03 am »
Below is the open tickets that have a Milestone set, which in most cases is not correct.

#    Milestone    Owner    Summary
1265    -    Next_Nightly    -    none    -    Patch for Linux-3.1.x
1262    -    Next_Nightly    -    bluehazzard    -    Status bar
1192    -    Next_Nightly    -    none    -    Shift + tab bug
1083    -    Next_Nightly    -    none    -    Fix multiple instances when "Use an already running instance" is checked"
1027    -    Next_Nightly    -    none    -    Auto-complete didn't work with using cptr = const * type (svn 12207)
992    -    Next_Nightly    -    none    -    An unhandled exception
943    -    Next_Nightly    -    Teodor Petrov    -    Use system hotlight color for start page links
928    -    Next_Nightly    -    Teodor Petrov    -    SmartIndent doesn't add closing brackets properly
922    -    Next_Nightly    -    Teodor Petrov    -    Debugger breakpoints with invalid fullname path
900    -    Next_Nightly    -    bluehazzard    -    Update for plugin script
778    -    Next_Nightly    -    bluehazzard    -    Sorting the output of the Vera++/cppchecker
600    -    Next_Nightly    -    none    -    Project's options not overwriting Global ones
411    -    Next_Nightly    -    Teodor Petrov    -    CB becomes unusable if the project is modified when build options is open on Linux
305    -    Next_Nightly    -    Teodor Petrov    -    Assert failure: invalid encoding value in wxCSConv ctor
286    -    Next_Nightly    -    ollydbg    -    CC crash when closing workspace
270    -    Next_Nightly    -    Morten MacFly    -    Projects do not build when swapping source files.
246    -    Next_Nightly    -    Jens Lody    -    Project loading/layout speedup
224    -    Next_Nightly    -    ollydbg    -    Duplication in documentation tooltip
174    -    Next_Nightly    -    Teodor Petrov    -    Breakpoints removed from editor are not removed from GDB
169    -    Next_Nightly    -    Teodor Petrov    -    Predefined user commands for debugger plugin
145    -    Next_Nightly    -    ollydbg    -    Code completion ignores parameters of catch-clauses
42    -    Next_Nightly    -    none    -    Filling empty line by spaces instead of TAB character
38    -    Next_Nightly    -    none    -    ESC does not closes just opened modal dialogs
1043    -    Next_Release    -    none    -    Feature Request: Code::Blocks compiling in C#!
980    -    Next_Release    -    none    -    Debugger Problem Error
959    -    Next_Release    -    Teodor Petrov    -    Editor: code folding bar artefacts in HiDPI
930    -    Next_Release    -    none    -    wxGTK3 horizontal scrollbar: some part of a long line always stays off the screen
855    -    Next_Release    -    none    -    Ctrl+Z after paste the xml string from cutting a control would cause Codeblocks crash
209    -    Next_Release    -    Teodor Petrov    -    Bug in debugger logic
206    -    Next_Release    -    none    -    Precompiling headers fails with modern versions of GCC
129    -    Next_Release    -    none    -    doxyblocks block comment bug
128    -    Next_Release    -    Morten MacFly    -    Changing compilers leaves old options laying around
127    -    Next_Release    -    ollydbg    -    Code completion fails with complex declarations/definitions
120    -    Next_Release    -    Teodor Petrov    -    folding causes incorrect display, occasionally lines of code vanish
119    -    Next_Release    -    none    -    automatic generation of close curly brace
118    -    Next_Release    -    none    -    depslib adds unnecessary dependencies which cause unnecessary recompilation in some cases
117    -    Next_Release    -    none    -    search replace in box selection mode replaces outside of box
108    -    Next_Release    -    none    -    App crashes when pressing F9 / compile+run and there are special characters in the path
99    -    Next_Release    -    Morten MacFly    -    ThreadSearch and Lib Finder plugins depend on wxSmith plugin (windows installer problem)
97    -    Next_Release    -    none    -    Tab context menu not aware of project switch
95    -    Next_Release    -    none    -    wrong project is executed if switching projects during build-and-run
88    -    Next_Release    -    none    -    Code completion mouse hover tooltip is always active
83    -    Next_Release    -    none    -    codecompletion's setting not saved correctly
81    -    Next_Release    -    none    -    Patch for option to automatically select a run target
78    -    Next_Release    -    none    -    Patch Autoversionning add onn
77    -    Next_Release    -    none    -    Patch compiler LCC / missing librairies
76    -    Next_Release    -    none    -    Patch compiler LCC/LCC64
75    -    Next_Release    -    none    -    Patch for running elevated program on Windows Vista and after
70    -    Next_Release    -    none    -    Jump to first search result on/off
65    -    Next_Release    -    none    -    Patch for saving/restore small window size position
63    -    Next_Release    -    none    -    ToolsPlus + Keybinder
50    -    Next_Release    -    none    -    Add option to play an alert sound when compilation finishes
49    -    Next_Release    -    Teodor Petrov    -    Add flag to exclude some project files from search
48    -    Next_Release    -    bluehazzard    -    Print dialogue appears for every file when batch printing multiple files
47    -    Next_Release    -    ollydbg    -    Show call tip of the constructor function
44    -    Next_Release    -    Teodor Petrov    -    Code completion when typing in multiple selections simultaneously
43    -    Next_Release    -    none    -    Code complete-keyword final
31    -    Next_Release    -    ollydbg    -    restrict keyword and auto-completion
27    -    Next_Release    -    none    -    function returning struct confuses codecompletion for close brace
5    -    Next_Release    -    Morten MacFly    -    Support Visual Studio 2012
1030    -    Release_xx.yy    -    Lieven de Cock    -    Entry Point not Found on Windows XP
971    -    Release_xx.yy    -    none    -    C::B-Library Finder Plugin hangs on auto-detection scan
958    -    Release_xx.yy    -    none    -    Bug in Editor
950    -    Release_xx.yy    -    none    -    Bpo shortcuts doesn't work anymore
944    -    Release_xx.yy    -    none    -    Signing requirements for OSX builds...
783    -    Release_xx.yy    -    Teodor Petrov    -    Folding: "Fold all on open" performs 'Toggle All', instead of 'Fold All'
753    -    Release_xx.yy    -    none    -    [Debugger/nightly Oct 2018] no break point options by right click in break points frame any more
613    -    Release_xx.yy    -    none    -    Regular expressions search/replace issue within text files with special characters (german Umlaute like , , ...)


Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1201
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #20 on: September 23, 2022, 11:08:12 am »
Quote
Should someone change the tickets to remove the owner where it is set to Teodor Petrov?
Probably, but the tickets he owned are debugger-related or relevant, so IMHO if we remove their owner they should be marked as Accepted (or use a similar method to differentiate)

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 678
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #21 on: September 23, 2022, 01:00:43 pm »
Is the SF ticket process documented anywhere or what the fields are used for documented anywhere?

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 1201
Re: Sourceforge Ticket review - feeback on easy tickets to close part 1
« Reply #22 on: September 23, 2022, 01:21:28 pm »
I do not think so.