Author Topic: When is the next version coming out?  (Read 13423 times)

Offline Card

  • Single posting newcomer
  • *
  • Posts: 1
When is the next version coming out?
« on: August 12, 2015, 01:21:09 am »
I've always liked Code::Blocks, and I've used it for years. The latest version, 13.12, came out over a year and a half ago (quickly approaching two!). Has the development stopped? Or can we expect a huge update with various dark themes and multi language and scripting support? :D

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #1 on: August 12, 2015, 01:26:21 am »
Development hasn't stopped. Just there is no official release.
You can check the nightlies to see what are the improvements.

The dark themes stuff isn't happening, because no one is contributing themes as far as I know.
<debugger plugin maintainer>
(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 Croydon

  • Single posting newcomer
  • *
  • Posts: 3
Re: When is the next version coming out?
« Reply #2 on: August 14, 2015, 09:40:14 pm »
Code::Blocks should really move away from Sourceforge after all what did happen and is happening there.

Also the project team should provide more regular new information, the project seems dead for everyone who isn't digging really deep into it.

I would recommend to move to GitHub and also open source the website, so people can also help with that. The current one is outdated and looks aged.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #3 on: August 14, 2015, 09:45:57 pm »
I'm not sure how the site works, but if you're interested in helping improve the look we could probably think how you can do it.

Also if you follow the night build subforum or the code history page on sf.net you'll know that there is activity in this project.
Also we have some clones of the main repo on github, so you can follow them. Mine is manually updated every 2-3 days.
<debugger plugin maintainer>
(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 eckard_klotz

  • Almost regular
  • **
  • Posts: 145
Re: When is the next version coming out?
« Reply #4 on: August 26, 2015, 03:03:27 pm »
Hello Croydon.

Quote
Code::Blocks should really move away from Sourceforge after all what did happen and is happening there.

What are you meaning???

Quote
I would recommend to move to GitHub and also open source the website, so people can also help with that. The current one is outdated and looks aged.

Changing the provider would not help to update the website if the developer decide that it is more important to spent the effort in the product itself (what I definitely prefer). As far as I understand it you can add some pages in the wiki or at least you can provide you information in the forum.

Quote
... the project seems dead for everyone who isn't digging really deep into it.

If clicking on the forum-button is digging deep I ask my self what amount of information you expect on the main-page and what kind of confusion this causes for a new-bee.

The project had already to move since the provider used before has closed his service. And I would recommend definitely not spent some effort to change again especially if I think about what this means for older users which already know where to find what and who are using SVN.

Best regards,
                      Eckard. 

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9414
Re: When is the next version coming out?
« Reply #5 on: August 26, 2015, 05:19:38 pm »
Also the project team should provide more regular new information, the project seems dead for everyone who isn't digging really deep into it.
Well on SourceForge, with every nightly you have a new news entry. And according to the statistics (downloads / accesses) the projects seems well represented and acknowledged.

However, surely we could do better. :-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Croydon

  • Single posting newcomer
  • *
  • Posts: 3
Re: When is the next version coming out?
« Reply #6 on: August 27, 2015, 06:04:37 pm »
I'm not sure how the site works, but if you're interested in helping improve the look we could probably think how you can do it.

Also if you follow the night build subforum or the code history page on sf.net you'll know that there is activity in this project.
Also we have some clones of the main repo on github, so you can follow them. Mine is manually updated every 2-3 days.

I'm not really a good designer, but I could change outdated stuff and other minor things. However, e.g. the GitHub workflow makes contributing so much easier. People don't want to invest 2 hours just to get started if they don't want to become long run contributors. It's less about me, but more about attracting more contributors in general by reducing the formal steps. You can't simple fork, commit and create a pull request and discuss the changes on SourceForge.

An inoffical mirror is one thing. An offical mirror where I can send requests is another thing  :)


Hello Croydon.

Quote
Code::Blocks should really move away from Sourceforge after all what did happen and is happening there.

What are you meaning???

SourceForge is modifying offical installers from popular projects. They're adding adware to it against the will of the project owners. See for e.g.:

Gimp: http://www.gimp.org/news/2015/05/27/sourceforge-what-the/  & http://www.gimp.org/news/2015/05/27/gimp-projects-official-statement-on-sourceforges-actions/
VLC media player: https://blog.l0cal.com/2015/06/02/what-happened-to-sourceforge/
Notepad++: https://notepad-plus-plus.org/news/notepad-plus-plus-leaves-sf.html

You can't trust a platform anymore which does stuff like that.


Quote
I would recommend to move to GitHub and also open source the website, so people can also help with that. The current one is outdated and looks aged.

Changing the provider would not help to update the website if the developer decide that it is more important to spent the effort in the product itself (what I definitely prefer). As far as I understand it you can add some pages in the wiki or at least you can provide you information in the forum.
 

Again, switching to GitHub reduces the barrier for contributing. The developers of CB don't need to concentrate that much on the website. But when people create pull requests with reasonable changes I'm pretty sure they getting welcomed by the team  :)


Quote
... the project seems dead for everyone who isn't digging really deep into it.

If clicking on the forum-button is digging deep I ask my self what amount of information you expect on the main-page and what kind of confusion this causes for a new-bee.


Easy, the website has a news section. So I'm expecting that it's getting regular updates. Also the RSS feed depends on these news and the landing page gives always a "more offical" impression than a forum to the visitors.
Also it contains a lot of dead links and the offical last stable release is two years ago. So yes, just talking about the landing page, one can't really see any progress on the project.

The project had already to move since the provider used before has closed his service. And I would recommend definitely not spent some effort to change again especially if I think about what this means for older users which already know where to find what and who are using SVN.

Well, users (not CB developers, not people who self-compile) don't care where the source code is.
People, who just grap the source code because they compile it on their own, doesn't really care either. Moreover, you can still perform a svn checkout on a GitHub repository, so this group of people doesn't need to change anything, except the URL.

It would be a change for CB developers, yeah. But honestly changes are normal and not avoidable. Of course, don't do everything which would be theoretically possible, but effort < benefit is given in this case more than once.

And when I should give a prognosis then I would say that SourceForge is getting closed down in a few years. Many, many projects are migrating away from SourceForge and SF offers nothing which isn't replaceable or even better somewhere else.
The same did happen with Google Code, but at least Google Code didn't modify projects or displayed "download now!" advertising which leads to malware.

Also the project team should provide more regular new information, the project seems dead for everyone who isn't digging really deep into it.
Well on SourceForge, with every nightly you have a new news entry. And according to the statistics (downloads / accesses) the projects seems well represented and acknowledged.

However, surely we could do better. :-)

Right, but from time to time there should be a summary, a posting about where the jouney is going, the "big picture" only the team can see.  :)
« Last Edit: December 07, 2015, 04:29:48 pm by Croydon »

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9414
Re: When is the next version coming out?
« Reply #7 on: August 28, 2015, 07:11:49 am »
However, e.g. the GitHub workflow makes contributing so much easier.
I hear that so many times... However with SVN its the same:
1.) Checkout
2.) Change
3.) Run the command "svn diff > my.patch" in your working copy
4.) Post "my.patch" to the patch tracker.
The only "issue" is, that if you create new files you'll need to add a "svn add mynew.file" command before 3.).

I don't understand why this is too hard or harder than GIT. I still believe whoever wants to contribute can take these steps, too. Nevertheless we have GIT mirrors, so what is this all about, actually?

And btw: In 95% of the cases we have to modify the patch because the C::B style is not followed or the change is buggy. So not simply "pulling" is also an important quality assurance!
« Last Edit: August 28, 2015, 07:13:35 am by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Easior Lars

  • Multiple posting newcomer
  • *
  • Posts: 44
Re: When is the next version coming out?
« Reply #8 on: August 28, 2015, 07:34:01 am »
I don't understand why this is too hard or harder than GIT.
I don't agree with you. If I clone a repository by GIT, then I can change some files and commit them. Next time I can continuous to pull and merge modifications to local branch. However, I'm afraid that I can't commit and merge any modification in local repository when I use subversion as a non-privilige user.
« Last Edit: August 28, 2015, 02:46:27 pm by Easior Lars »
Development Environments:GCC+CodeBlocks+wxWidgets
Developing Languages:Bash+Python+C/CPP+LaTeX
Developer Utils:Emacs+GIT+OpenSSH+GPG
OS:Mac OS X, Gentoo/Kali Linux/Fedora/CentOS, MS Windows
Blog:http://easior.i11r.com

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9414
Re: When is the next version coming out?
« Reply #9 on: August 28, 2015, 01:18:50 pm »
I'm afraid that I can't commit and merge any modification in local repository when I use subversion.
If that is the major advantage you would like to achieve then why don't you simply make a GIT clone of the SVN repo using git-svn?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline stahta01

  • Lives here!
  • ****
  • Posts: 5834
    • My Best Post
Re: When is the next version coming out?
« Reply #10 on: August 28, 2015, 01:33:04 pm »
I'm afraid that I can't commit and merge any modification in local repository when I use subversion.
If that is the major advantage you would like to achieve then why don't you simply make a GIT clone of the SVN repo using git-svn?

On windows it can take a long time on a slow machine; when I started doing it. It was normal to take more than 36 hours.
But, I am now dual booting windows (with Debian 8 ) and it takes much less time to do all the svn2git steps on Linux and just clone my repo on windows.
Takes less than 2 hours of work on Windows.

My Git Repo is here https://github.com/stahta01/codeblocks_svn2git_metadata

Tim S.
« Last Edit: August 28, 2015, 01:41:27 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline teto

  • Almost regular
  • **
  • Posts: 127
Re: When is the next version coming out?
« Reply #11 on: August 28, 2015, 03:18:31 pm »
I don't know for others but I've stopped visiting/downloading from Sourceforge due to these events. Even before that, the site looks bloated with ads, and the interface old ("bad" old) IMO.
I've never worked much with SVN because it was so hard to work with, any merge failed and the necessity to have an internet connection was pretty bad. Then I discovered git and never looked back: better merging  (surely subversion improved that during the past 4/5 years I've not used it) and being able to play with commits/branches locally, having different remotes to allow for private and public patches etc... is just mandatory for big patches.

I also find the github workflow very good.

Quote
If that is the major advantage you would like to achieve then why don't you simply make a GIT clone of the SVN repo using git-svn?
git-hg works but I wonder how fares git-svn, I imagine the backends are very different.
Quote
And btw: In 95% of the cases we have to modify the patch because the C::B style is not followed or the change is buggy
In nearly all projects I know, the uploader has to fix his patch himself. I believe this is a good approach as it makes future contribtuions more likely (and with github, updating the patch does not clutter communications, you usually just force a  push and github notifies that the PR has been updated).


Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #12 on: September 01, 2015, 02:07:58 am »
Why do you care for svn merges, when contributing to cb?

Also there are several git clones of the svn repo, you can use them to contribute.
The only requirement are:
1. keep your branches rebase-able, so they can be integrated in the main repo.
2. post pull-request here or in the issue tracker on sf.net, not github, so everybody can see them.

I agree that the recent practices of sf.net are a bit alarming...

p.s. This is my git clone of the main repo https://github.com/obfuscated/codeblocks_sf, it is kept up to date manually and this is the only repo I use, so it is known to be working.
<debugger plugin maintainer>
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9414
Re: When is the next version coming out?
« Reply #13 on: September 01, 2015, 08:21:09 am »
To summarise: You can choose between GIT and SVN. Pick your favourite and start contributing! :-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #14 on: November 04, 2015, 09:56:35 am »
Development hasn't stopped. Just there is no official release.

Why not? Is the development version so buggy that it can't be released? This is getting on my nerves.

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5008
Re: When is the next version coming out?
« Reply #15 on: November 04, 2015, 06:48:52 pm »
we are working on it, normally still this year.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #16 on: November 04, 2015, 09:13:45 pm »
Why not? Is the development version so buggy that it can't be released? This is getting on my nerves.
Please try a night build and tell us if there are problems we need to fix.
<debugger plugin maintainer>
(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 Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #17 on: November 05, 2015, 10:03:22 am »
Please try a night build and tell us if there are problems we need to fix.

No. I'm going to wait for the release version and then tell if something is wrong. You developers should know the program inside out, not the users. And you really should release more often, it's better that way, because then more users will report bugs etc. You can get sloppy with indefinite development version (night builds), because then bugs and unfinished features are ok and "will be" fixed in distant future.

Offline frithjofh

  • Regular
  • ***
  • Posts: 371
Re: When is the next version coming out?
« Reply #18 on: November 05, 2015, 02:10:51 pm »
although I am perfectly fine with nightly builds, I am afraid, he is right...

most users want a version. period.

and then, yes, every time I look into some piece of code of c::b, I get the feeling too, that there are many rather sloppy corners...

the event system, the multithreading, many dialogs, even logical errors...

so, as I said, I am fine with the nightlies, but I understand his point
architect with some spare time  -  c::b compiled from last svn  -   openSuSE leap x86_64  -  AMD FX-4100

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #19 on: November 05, 2015, 07:32:59 pm »
the event system, the multithreading, many dialogs, even logical errors...
Post patches and bug reports, please.
<debugger plugin maintainer>
(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 thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: When is the next version coming out?
« Reply #20 on: November 05, 2015, 08:45:20 pm »
There's a few things that I'd like to comment on here:
Quote
You are doing everything wrong. Code::Blocks sucks. I'm not going to tell you what is wrong, you have to know. I'll tell you after the release. (paraphrased)
Right. That's not going to get you a release any faster, nor a product that's more according to your wishes. If you have something that doesn't work, it's time to tell before a release comes out, not after. Unless of course you only complain because you like complaining.

Quote
SourceForge is modifying offical installers from popular projects. They're adding adware to it against the will of the project owners
That is an outright lie. You should be really careful about what you are saying because it can have much more drastic consequences for your person than you are probably aware of.

Sourceforge did (and does) add adware to installers, but only after the project owners (who get revenue for doing so) have opted in.

Our project has been popular for a long time. It is currently ranked #16 in development and has been in the top 10 for several years (was ranked #2 after last release, it also has been featured as project of the week and whatever it's called, too). At no point in time did Sourceforge secretly or against our will (or at all!) add adware to any of our executables/installers. No adware is currently contained in our installers, and we are not making any money from such a channel (Yiannis does receive one or the other donation on occasions, but on the yearly average, it's less than what renting the server for the website and the forum costs).

Sourceforge indeed does display a considerable amount of ads on their website. Guess what, a lot of websites do that, it's what they live from.

Quote
"Github is so much better than Sourceforge. Git rules and SVN is for losers." (paraphrased)
Yeah, OK. You can choose whichever revision control system and provider you want, the difference is not big. Unlike common folklore, Git has no significant advantages over SVN, unless you work on something the size of the Linux kernel and want a similar workflow like on the Linux kernel (including sending tar files via email, which according to Torvalds is vastly superior to using Subversion). For a project the size of Code::Blocks and a team the size of our team, Subversion works very well.

Please feel free to use what you like, but stop trying to press us into using something different simply because you like it better for some ideologic reason.

In particular, this:
Quote
switching to GitHub reduces the barrier for contributing
is not true. Checking out takes typing 6 characters plus the repository's name, or two clicks with the mouse (depending on what you use). Making a patch, which is factually the equivalent to "committing a branch" takes the same amount of work. Yes, your patch will not be merged to master (or trunk, or whatever you call it). But that won't happen without someone reviewing it anyway, not with Git either.

Quote
However, I'm afraid that I can't commit and merge any modification in local repository when I use subversion as a non-privilige user.
That is true, but it is also something that is explicitly not wanted. It's why there is an authorative server with access control lists in the first place. While having two thousand people clone repositories and commit 25 branches per day as they like sounds like an awesome idea, it is not nearly as awesome unless you have a team of two dozen people dedicated to reviewing these. We don't have that.

The need of producing a clean, working patch which only ever gets committed after applying cleanly without conflicts and being reviewed and tested is something that works well for us (even so, it is often more than what we can cope with time-wise).
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline raynebc

  • Almost regular
  • **
  • Posts: 135
Re: When is the next version coming out?
« Reply #21 on: November 05, 2015, 10:45:41 pm »
I'll just come into the discussion to agree that nightly builds are super easy and convenient to use.  For the program I work on, I use a similar/simpler strategy (only the modified executable/resource files) because it allows me to quickly add fixes and new features without the hassle of creating a full package.  My users don't care how often a formal version release is made and it really is not important compared to the stability of the current build.  I ignore users that whine about something and refuse to give any helpful information or valid reasons for complaints, as they are not helpful.  Codeblocks is pretty stable, I rarely see it crash or lock up.

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #22 on: November 05, 2015, 10:50:21 pm »
Right. That's not going to get you a release any faster, nor a product that's more according to your wishes. If you have something that doesn't work, it's time to tell before a release comes out, not after.

Please quote the actual message. But assuming you were talking about my message then this is what I'm going to say: don't try to turn this on me. YOU are the developers, not me. I have no obligation to try out unfinished software, as if it would make any difference on when the next version is released. Usually any normal software has an official release, which (the content and quality of the software) should be known for the developers. I mean what kind of developers are waiting for users to find bugs and even write patches? Why do you even call yourself developers?
« Last Edit: November 05, 2015, 10:52:02 pm by Krice »

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7177
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: When is the next version coming out?
« Reply #23 on: November 05, 2015, 11:09:51 pm »
Right. That's not going to get you a release any faster, nor a product that's more according to your wishes. If you have something that doesn't work, it's time to tell before a release comes out, not after.

Please quote the actual message. But assuming you were talking about my message then this is what I'm going to say: don't try to turn this on me. YOU are the developers, not me. I have no obligation to try out unfinished software, as if it would make any difference on when the next version is released. Usually any normal software has an official release, which (the content and quality of the software) should be known for the developers. I mean what kind of developers are waiting for users to find bugs and even write patches? Why do you even call yourself developers?
Did you her of free and open source software ?
Do you know what it means to develop software in your spare time, besides your family, your friends, your job etc.

It seems, that you do not know much about software developping at all.

Even if you have a big team, you will never be able to find all bugs, so you need alpha, beta, etc testers or you will never be able to get stable software.
Nightly builds are a real good way to have many testers and to react (as) fast (as possible), if somebody finds a bug.

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #24 on: November 06, 2015, 08:53:08 am »
Do you know what it means to develop software in your spare time, besides your family, your friends, your job etc.

Yes I know. It's lot easier than professional development, because you don't have a deadline or any responsibility to your company or users for success. You can do anything you want and take all the time you need for that, and no one can say anything about it.

Quote
Even if you have a big team, you will never be able to find all bugs, so you need alpha, beta, etc testers

Of course you can find if not all then most bugs. No beta testers needed for that, because obviously you can test everything by yourself and not only that, developers are in better position to do that since they should know how the program works, what features are new etc.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #25 on: November 06, 2015, 09:07:37 am »
Krice:
You're missing the point quite badly. No one does C::B as a job, no one is paid for the work he/she is doing.
So most people work on C::B for fun or because they need certain features.
Also most of the developers have some workflow that they are testing everyday and it is known to work.
We're not using all features of C::B everyday. I've even disabled some of the plugins and I've never used them since.

Any feature outside our workflows might be broken beyond repair and we might not know it. We have no QA that clicks on the buttons randomly.
And the reason is simple - no one has stepped up to do the job. We do night builds, to make it possible random people to test newer features and code.
So if you want to help pick a nightly and test if everything you do with C::B works correctly.
If it doesn't report the issues here or on the sf page.
Otherwise just wait and get stuck with what it is released, hopefully soon, but don't expect it to be bug free, nor regression free.

To repeat once more - we're not a formal organisation and people cannot be forced to do things they are not interested doing!
This is how it works and nothing can be done about it.
<debugger plugin maintainer>
(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 Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #26 on: November 06, 2015, 12:46:55 pm »
And the reason is simple - no one has stepped up to do the job.

Version 13.12 credits shows you have 13 programmers. I would say it's a big team for open source project. Surely one of them could test the program? You really can't expect users to do that job for you and even worse, put the blame on users for not testing the program and reporting bugs as the reason why the next release version can't be completed.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 5834
    • My Best Post
Re: When is the next version coming out?
« Reply #27 on: November 06, 2015, 03:34:22 pm »
And the reason is simple - no one has stepped up to do the job.

Version 13.12 credits shows you have 13 programmers. I would say it's a big team for open source project. Surely one of them could test the program? You really can't expect users to do that job for you and even worse, put the blame on users for not testing the program and reporting bugs as the reason why the next release version can't be completed.

So, you know very little about program testing; I could spend months testing Code::Blocks and likely would still miss bugs.
Testing is NOT a easy job to do well! You have all the different OSes and Compiler that need tested; then, you have all the CB Plugins that need tested.

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #28 on: November 06, 2015, 08:37:55 pm »
Version 13.12 credits shows you have 13 programmers.
Most of them are inactive at this moment.

I would say it's a big team for open source project. Surely one of them could test the program? You really can't expect users to do that job for you and even worse, put the blame on users for not testing the program and reporting bugs as the reason why the next release version can't be completed.
We don't blame users that there is no release. Nor we blame users for anything.
You're the one blaming us that we don't release. If you want to help, grab a night build and report any problems that affect your workflow, otherwise just wait for the next release.

And yes we test the software by using it, but this is something completely different from a QA team testing some piece of functionality and trying to brake every feature advertised by developers. C::B's team has a QA team of zero as are most of the smallish open source projects.

<debugger plugin maintainer>
(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 Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #29 on: November 07, 2015, 12:23:21 pm »
If you want to help, grab a night build and report any problems that affect your workflow, otherwise just wait for the next release.

That's directly throwing the responsibility to me (and any users). "If you don't do anything, sorry, we can't finish the next release version." Well you know what, I don't need it. I'm using mainly Visual Studio (free version) and it's no wonder why. Even the ancient 2010 version is better than current Code::Blocks.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #30 on: November 07, 2015, 12:43:04 pm »
If you're interested in C::B getting better for you and your workflows then this is the only way it is going to happen. You have to get a little involved.
There is nothing holding the release, just we have to do it. There are no blocker issue and so on. And to give you a hint - it will work like the latest night builds, it won't be magically better.

About VS 2010. Are you surprised? The VS team is probably 100+ people working on it as their main job. The funny thing is that C::B is better in some aspects (better projects, some integrated editor features).
<debugger plugin maintainer>
(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 jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7177
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: When is the next version coming out?
« Reply #31 on: November 07, 2015, 01:36:07 pm »
If you want to help, grab a night build and report any problems that affect your workflow, otherwise just wait for the next release.

That's directly throwing the responsibility to me (and any users).
That's community driven development, accept it or stop whining.

"If you don't do anything, sorry, we can't finish the next release version." Well you know what, I don't need it. I'm using mainly Visual Studio (free version) and it's no wonder why. Even the ancient 2010 version is better than current Code::Blocks.
So my suggestion, just shut-up and stop trolling here.

Offline frithjofh

  • Regular
  • ***
  • Posts: 371
Re: When is the next version coming out?
« Reply #32 on: November 07, 2015, 04:53:12 pm »
++jens
architect with some spare time  -  c::b compiled from last svn  -   openSuSE leap x86_64  -  AMD FX-4100

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2065
Re: When is the next version coming out?
« Reply #33 on: November 07, 2015, 06:05:02 pm »
The previous comment += 1;

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #34 on: November 07, 2015, 08:16:58 pm »
That's community driven development, accept it or stop whining.

Really. I thought C::B developers were a team of programmers? By the way, who gets the donations of this project? In some cases open source projects can get a substantial amount of money in donations, but some people never see any of it, even they can give a lot of their time and effort for the project. Not only that, you are asking people to help, in fact demanding that. I wouldn't exactly call that an equal community.

Offline Folco

  • Regular
  • ***
  • Posts: 343
    • Folco's blog (68k lover)
Re: When is the next version coming out?
« Reply #35 on: November 07, 2015, 09:52:57 pm »
Oh my god, how you Krice are afflicting...
You don't have to love C::B, but if you don't like it, just don't use it and stop trolling the devs, they have something else to do instead of answering your nastiness.
You could just shut up, considering the huge amount of free work contributed by the main devs and other people, across the years.
And if you're not happy with C::B, just write your own...

I hadn't read something so deplorable since a long time...
Kernel Extremist - PedroM power

Offline scarphin

  • Lives here!
  • ****
  • Posts: 644
Re: When is the next version coming out?
« Reply #36 on: November 07, 2015, 10:06:23 pm »
I hadn't read something so deplorable since a long time...
I second that.

Offline raynebc

  • Almost regular
  • **
  • Posts: 135
Re: When is the next version coming out?
« Reply #37 on: November 08, 2015, 02:53:23 am »
If you want to help, grab a night build and report any problems that affect your workflow, otherwise just wait for the next release.

That's directly throwing the responsibility to me (and any users).
No, that's saying bugs get fixed faster when users participate in the testing process.  Otherwise developers only have the possibility of fixing bugs they themselves discover.  It's perfectly clear you really have no clue how no/low-budget code development works, and if you're just going to complain instead of be helpful or at least silent you might as well just go away because if it's not obvious to you yet, nobody that puts real work/testing into this project appreciates your whinging.

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #38 on: November 08, 2015, 10:45:56 am »
It's perfectly clear you really have no clue how no/low-budget code development works

Developers decide how it works. If you as a programmer also check out how the program works you are doing the testing and it's perfectly possible. I've done it myself. Some developers just think it's ok to let the users find bugs. This has been I think a problem even in commercial development. Just think of almost all modern PC games which are by default released with tons of bugs, which then are patched when players complain about them. I think it's not ok. You should check out your own stuff before releasing it. It's not that hard.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #39 on: November 08, 2015, 12:36:23 pm »
Krice: What do you want to achieve with your posts?
<debugger plugin maintainer>
(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 Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #40 on: November 08, 2015, 12:56:21 pm »
Krice: What do you want to achieve with your posts?

World peace? I'm not trying to achieve anything, these are just my opinions about this situation where the last version was released two years ago. I'm just wondering and it doesn't help if you keep arguing that it's all because no one is testing the software. Isn't there a lot of people using night builds?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 10054
Re: When is the next version coming out?
« Reply #41 on: November 08, 2015, 03:48:27 pm »
Sorry but we're not arguing that the release is not happening because no one is testing it.
It is not released, because we've not released it. And we'll release it when we decide to release it.  8)
<debugger plugin maintainer>
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9414
Re: When is the next version coming out?
« Reply #42 on: November 08, 2015, 07:17:31 pm »
By the way, who gets the donations of this project?
I can tell you that we don't get much. The donation we get (however) do usually not even cover the costs for server and hosting.

However, instead of donations what we get more often is posts like yours. This is helpful and makes us wish to work even harder for free, as you can imagine. Thank you.

For now it is as simple as we didn't manage / find the time to do a next release although its in the planning since August. Period.
« Last Edit: November 08, 2015, 07:19:47 pm by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline cacb

  • Regular
  • ***
  • Posts: 345
Re: When is the next version coming out?
« Reply #43 on: November 08, 2015, 07:25:44 pm »
I can tell you that we don't get much. The donation we get (however) do usually not even cover the costs for server and hosting.

This thread reminded me to send a small donation. Thanks for your work, guys.

Offline teto

  • Almost regular
  • **
  • Posts: 127
Re: When is the next version coming out?
« Reply #44 on: November 08, 2015, 08:31:14 pm »
Quote
However, instead of donations what we get more often is posts like yours. This is helpful and makes us wish to work even harder for free, as you can imagine. Thank you.
I hope it is some kind of humor :) at least on the nighlties forum I feel the community constructive and thankful for your work. I know I am so let me say thanks again for your time and I believe more people think that way rather than krice's. All the bugs I reported were fixed quite fast. I want to thank everyone and especially obfuscated and jen's for their repo/help.

Keep up the good work and I am looking forward the day neovim gets embedded into codeblocks :) (sorry I didn't mean to finish on a troll :) )
« Last Edit: November 08, 2015, 08:37:03 pm by teto »

Offline raynebc

  • Almost regular
  • **
  • Posts: 135
Re: When is the next version coming out?
« Reply #45 on: November 08, 2015, 09:14:50 pm »
You should check out your own stuff before releasing it. It's not that hard.
Are you really so arrogant to think you can find all bugs in your own software without any help, or are the programs you develop simple enough for this to be achievable?  I tend to believe most serious developers DO look for bugs in their own code.  I try to find bugs in mine, but the more complicated a program is, the harder it is to eliminate all bugs.  I thoroughly comment my code, test new features and use 3 static code analysis programs (including Coverity Scan, which uses one of the leading commercial analysis tools) looking for bugs and bugs STILL happen because as a human, I am imperfect.  The more eyes there are, the faster a bug will be outed because different people use software in different ways and use different input files.  Users of commercial software contribute to a project when they buy it.  Users of open source software contribute when they use a program and report any problems they find.  If they go out of their way to try to find bugs, or submit code/patches that's even better.  If you're of the mindset that you should get a perceived bug-free IDE that has been professionally tested by a paid QA team, go back to Visual Studio.

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: When is the next version coming out?
« Reply #46 on: November 09, 2015, 09:15:13 am »
I thoroughly comment my code, test new features and use 3 static code analysis programs (including Coverity Scan, which uses one of the leading commercial analysis tools) looking for bugs and bugs STILL happen because as a human, I am imperfect.

This is off-topic, but since you asked. The most important change for me was when I switched from C to C++ and by that I mean real C++ with proper rules like constructor-destructor paradigm, following strict ownership etc. When you eliminate the usual suspects (raw arrays, careless use of pointers, etc.) it makes the source code very rigid and reduces the possibility of bugs happening in the first place. There has been a slow, gradual change from C to C++, but even today C is often used as a base of many open source projects. Which means there are hundreds of bugs. It's the direct result of C in large scale projects, you can't avoid it. Not only that, I think C++ (object-oriented paradigm) is poorly understood and difficult to be good at, which is sad considering how powerful it can be when used the proper way.

I'm also using static code analysis tools, like CppCheck. And two compilers at the same time, VC and gcc. The final version is compiled in gcc.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: When is the next version coming out?
« Reply #47 on: November 09, 2015, 03:48:11 pm »
By the way, who gets the donations of this project? In some cases open source projects can get a substantial amount of money in donations, but some people never see any of it, even they can give a lot of their time and effort for the project.
The information about where that substantial amount of money goes is contained in my earlier post.

Quote
That's directly throwing the responsibility to me (and any users).
You are welcome to donate 95,000 per year, and I will take this responsibility as a full-time job, with an according service level. Until that happens, you will have to face reality, and if you are interested in getting a result (though from your shotgun-style posts I'm afraid you are really just trolling) you will need to come up with something more pragmatic than just complaining. You find a problem, report it. Or better yet, provide a solution.

As someone who claims to be experienced in software development, you will know that even given proper bug reports, it is often a challenge to reproduce and fix defects. I've had projects where nearly 50% of all reports supplied by users were either of the "what the hell is this about?" or of the "works for me" kind. Luckily, Code::Blocks is used almost exclusively by software developers (who, generally, write substantially better reports than the average end user).

Are you really so arrogant to think you can find all bugs in your own software without any help
That's a well-known and widespread psychological bias researched and published by Dunning and Kruger in the late '90s.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."