Author Topic: Bugs on SF for next release  (Read 577 times)

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 2023
Bugs on SF for next release
« on: December 11, 2017, 02:32:19 pm »
Hi, when is the release planed? Do you still want to add bug fixes?
I think i will find some time the next two weeks and would like to provide some patches.
The bug tracker on SF lists 65 open tickets for the next release. from this there are 35 bug reports. I could think for this to be easy to fix:
https://sourceforge.net/p/codeblocks/tickets/29/ this seems doable --> Not reproducible on windows and linux for me
https://sourceforge.net/p/codeblocks/tickets/49/ (at least the part where the target gets reseted every time: https://sourceforge.net/p/codeblocks/tickets/49/#99c1/5088 ) --> Patch posted
I have tried to reproduce this bug: https://sourceforge.net/p/codeblocks/tickets/53/ but for me the file opens fine. The character mentioned in line 5 is a blank for me. The same as in notepad++. So is this still a valid bug?
https://sourceforge.net/p/codeblocks/tickets/63/ (this is rather difficult and more a feature request then a bug report)
https://sourceforge.net/p/codeblocks/tickets/90/ (note for me to look into this as soon as i have my linux machine running again)
https://sourceforge.net/p/codeblocks/tickets/97/ this should be pretty easy
https://sourceforge.net/p/codeblocks/tickets/104/ (some pretty old bug, still valid for me at least with console applications)  --> Reason found, and a fix posted in the ticket
https://sourceforge.net/p/codeblocks/tickets/109/ Is this still valid? --> Can not reproduce on windows 7 wx3.0
https://sourceforge.net/p/codeblocks/tickets/100/ --> Patch posted

any other really important thing to do?
« Last Edit: December 14, 2017, 12:10:08 am by BlueHazzard »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11131
    • Travis build status
Re: Bugs on SF for next release
« Reply #1 on: December 11, 2017, 08:05:59 pm »
I think it is too late for almost all of them. But we won't reject them if you fix them. They won't make it in the release.

The most important thing to do is move to wx3.1 on windows and fixing some annoying wx3 related bugs on linux.
(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!]