Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: Kiryn on July 24, 2007, 11:34:38 pm
-
Why doesn't CB ever move away from RC2? Its been like that for 2 something years. Cause nightly builds suck. I'm afraid that C::B will turn into another dev-C++. Are the developer's that lazy?
-
Why doesn't CB ever move away from RC2? Its been like that for 2 something years. Cause nightly builds suck. I'm afraid that C::B will turn into another dev-C++. Are the developer's that lazy?
You saved my day :D :D :D :D
Seriously, just have a look at the daily changelog to see the devs working.
Why do you hate nightly builds?
You get updates every day!!!
An official release will just take away developing time, since it has to be maintained :D
-
A bit provocative huh? :?
Berlios' "Most Active All Time" stats....
1 IzPack 100.000
2 J2ME Polish 99.986
3 SIM IM 99.972
4 FreeNX 99.958
5 Goodies for the Xfce Desktop 99.943
6 SIP Express Router (ser) 99.929
7 Code::Blocks IDE 99.915
8 Smb4K 99.901
9 Stani's Python Tools 99.887
10 Player vs Player Gaming Network 99.873
Berlios "Most Active This Week" Stats
rank Project Name Percentile
1 J2ME Polish 100.000
2 Code::Blocks IDE 99.986
3 LinCityNG 99.972
4 Smb4K 99.958
5 btg 99.943
6 SIP Express Router (ser) 99.929
7 NWN Player Resource Consortium 99.915
8 PMB: Library Management System 99.901
9 BerliOS 99.887
10 SIM IM 99.873
Total : 7072 projects
Seems clear to me... good job guys :D
-
Then build a release then. Someone people actually want a full release not just keep constantly downloading nightly builds. Thats what I meant by lazy
-
OK, you may call us "lazy" because we haven't released an official version (be it 1.0 RC3 or 1.0 final or anything like that), but we have our reasons for not doing so, and BTW, we don't have an obligation to do it.
We could just take the current revision, tag it RC3, create the installer and release it, but I don't really think that would be a wise move. If you check the nightly builds forum you will find that every nightly fixes a few bugs, improves here and there, but also, sometimes, some new and serious bugs are introduced.
Right now we're trying to fix as many bugs as possible and also trying not to add new features (except if they're trivial ones). We are aware of the importance of a stable, or "almost stable" (as in Release Candidate), version, but... should we release it just because?
You don't have an obligation to constantly download nightly builds, in fact many of us use a single revision for quite a long time before updating to the most recent one.
What you can really blame us for is trying to get a 1.0 version very quickly and just after releasing RC2 doing such a lot of changes. I think we all agree all those changes were great, but perhaps we should have tried to stabilize what we had, create a branch, release a 1.0 final and what we're working on right now call it a 2.0 alpha/beta or something, but it's too late now.
So, don't be in such a hurry, RC3 is coming, but it will be released only when it be ready, and we all hope it will be soon.