Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: jondo on December 12, 2014, 03:27:55 pm
-
Looking at the SVN log, a lot has happened during this year. Let me suggest that you should do a Code::Blocks 14.12 release.
This would
* give a good first impression (sign of live) at the project homepage
* promote this year's most important new features
* give "drive-by" IDE evaluators something to install a little more easily than the nightly build.
-
I agree!
One release per year is just ok.
Even for bug fixes only.
-
Too late already. Next release will be at least 15.xx.
-
A kind suggestion to the devs would be to create a self-extracted archive (for windows) of the most stable nightly build and add it as link in main website.
This way could show some activity on the actual project and could possibly attract candidate volunteers with C::B's improvement.
Just my 2 cents.
Cheers.
-
A kind suggestion to the devs would be to create a self-extracted archive (for windows) of the most stable nightly build and add it as link in main website.
Why do you think a self-extracted archive is better than the current 7z file? :)
I personally don't think we can release a 14.xx release this year(15 days left for the current year), because there are some bugs to fix before the next release, so let's hope a 15.xx release.
-
Even if not 14.12, nor 15.03, the point is one release per year is good!
-
I think a normal release cycle with a minimum of a year and a max of 3 years seems good (like we have been doing).
But, I do think we need to think about a release when these things happen.
Release before major changes to the CB SDK.
Release after a stable MinGW GCC is released; right now the MinGW GCC releases are happening too often for this to be valid test for a release.
Release before major long term Linux Distros; no idea which Linux Distros we should target and how long before their release we would need to lead.
Tim S.