User forums > General (but related to Code::Blocks)
I love Code::Blocks
MortenMacFly:
--- Quote from: AndrewCot on April 13, 2022, 02:40:13 am ---One example of many:
https://forums.codeblocks.org/index.php/topic,24603.0.html
--- End quote ---
Oh dear... its not forgotten. The installer will be taken care of once there is a new release prepared. As I said before: please be more patient.
Also, don't forget that we always focus on stability. Just mindlessly applying tons of patches will not work. Therefore, careful testing is required. So you can help with that one quite well: Write test-cases and provide proof that patches you submit will not cause any harm under all conditions. That is what causes most delays. I, for example, have quite a bunch of patches applied for month before even considering applying it to SVN. If you are in a total hurry, you can contact me for specific patches via PM.
AndrewCot:
So you are saying that I have to work under different rules to other devs who supply patches in the SF ticket system or apply changes directly to the SVN tree? I have seen very scarce (by this I mean I cannot remember seeing any) SF ticket info by people for "Write test-cases and provide proof that patches you submit will not cause any harm". Is this a new requirement as there are no test harnesses to use to write test cases, with the exception of the CC that I have come accross?
I also see a allot of changes being applied to the SF SVN trunk that are peer reviewed and have no links to any tickets or forum posts. This makes the changes very hard or impossible to see if they are to do with a stability issue.
There have also been a number of SF SVN truck changes that have had to have changes applied within a day to fix them due to the lack of peer reviews and lack of testing.
I test my changes as best I can and also when changing complex or code that may break break code use it for an extended period of time before submitting a patch. As you are aware due to the complexities of the code base it is hard, unless you know all of the code inside out to test every code path that may be affected.
As for sending a PM I did for the installer and it got me where?
As for test cases, if this is a requirement then make it a requirement for every SVN change.
MortenMacFly:
--- Quote from: AndrewCot on April 13, 2022, 11:44:29 pm ---So you are saying that I have to work under different rules to other devs who supply patches in the SF ticket system or apply changes directly to the SVN tree?
--- End quote ---
No. All should work under the same conditions.
But of course we trust people more that have contributed over years.
And there is also a difference between fixing bugs and implementing new features. Fixing bugs is probably more relaxed as you can prove easily the bug is actually fixed. Implementing new features should actually require a discussion beforehand whether or not such a feature is desired. A lot of patches "to make things easier" caused actually the opposite.
So, I don't want you to stop, but it is no help to pup tons of patches and then abandon these after a while because nobody takes care immediately. Instead, try to push / move forward what you believe is important.
AndrewCot:
If other devs want info or help or have feedback or comments or updates on any of my patches I will help, but I will not push patches or chase things up where the other party (if there is another party) has gone AWAL or has stopped responding or no one is willing to look at the patch.
MortenMacFly:
--- Quote from: AndrewCot on April 15, 2022, 11:28:23 am ---If other devs want info or help or have feedback or comments or updates on any of my patches I will help, but I will not push patches or chase things up where the other party (if there is another party) has gone AWAL or has stopped responding or no one is willing to look at the patch.
--- End quote ---
As you "nagged me" (just as I suggested to do) I gave you a few comments on open tickets assigned to me.
Keep it that way. :-)
Navigation
[0] Message Index
[*] Previous page
Go to full version