About RC3

[Ceniza]

None.

[matthewjumpsoffbuildings]

drat

[PhyloGenesis]

You know, I'd b****, whine, and complain about it being delayed, but then I think, "How much did I pay for Code::Blocks?  Oh yeah." and then instead I say:

Wow, thank you guys, this program is awesome!  It's exactly what I was looking for to get away from MSVC++ 6.0.  I can't wait for rc3, I'm glad to hear it will be a stable version with many more features.  I like that it is open-source so I can learn from your coding, I love the fact that we can request features, that it has forum support, and that I can write my own plugins.  Finally, of course, I love it all even more because it's totally free!

Hopefully, I won't end up too busy with school to help you guys work on this!

[matthewjumpsoffbuildings]

do you have smilies turned of? i said "drat SMILE" not "drat RANT RAVE WHINGE BITCH". Chill out - i agree with you 100% and have no desire to rush the excellent job being done by the developers - so yea i was joking when i said drat....

[kylove]

RC3 probably when issued?
RC3 probably when issued?
RC3 probably when issued?
RC3 probably when issued?

[mandrav]

RC3 probably when issued?
RC3 probably when issued?
RC3 probably when issued?
RC3 probably when issued?

liuke520, I see you 're back. You should know the forum rules by now...

[cpprooky]

2 days without Night Build ?
Feels like RC3 is about to come ??  :lol:

[Game_Ender]

2 days without Night Build ?
Feels like RC3 is about to come ??  :lol:

I think not, it was mostly Berlios being broken that caused the lack of commits, which caused the lack of a nightly being released.

[kylove]

what time the RC3 Release ?

[Death Knight]

what time the RC4 Release ?  :lol:

[Phatency]

I really can't understand what these people think RC3 is going to change if they're already using nightly builds :P They're basically waiting for a version which has an installer and the word "stable" stamped on it, whoopee. I can understand the hype in some closed source release, but open source project with daily binary releases?

[darus]

I really can't understand what these people think RC3 is going to change if they're already using nightly builds They're basically waiting for a version which has an installer and the word "stable" stamped on it, whoopee. I can understand the hype in some closed source release, but open source project with daily binary releases?

It's not that easy. For example, you're a developer, that owns some project and want it to be supported by CodeBlocks. So, if there is some official version, you could test if your project is compatible with it, then post a label like "CodeBlocks 1.0 compatible" on it. So, it's guaranteed, that if some user downloads Codeblocks 1.0, it will work with your project.

But when new releases come each day (each night, to be more accurate  ), and all of them are equal, you can never tell, that your project is compatible with CB. There is always a possibility, that new build will ruin the compatibility.

When new version come with a reasonable intervals, say, once each 6 months, you can update your project to make it compatible with CB once again. But when there are constant changes in CB, supporting compatibility with it becames a burden to third-party projects.

[peso]

I Agree. The RC3 label is not important, it could be labled "2.0" or "39874" or "Yellowstone" or whatever. The important part is to have a release that is the same for many users. Stability (read "non-changing") is important to avoid rework of integration tests.

If such a label could be applied to a nightly build every 6 months, this would go a long way in this respect.

Of course an official release would be better, but no label - even with high quality code - does not meet this requirement.

Best regards,

[Jewe]

The RC3 label is not important

For me it is. my "quality manager" will not let me upgrade my building machine unless its a final or a RC..
so at the moment I am using the nightly and have rc2 on the build...
problem is that I can not open the project files with that rc2 made with the nightly.
so from time to time i need to use the rc2..

is does give you a good impression in how far c::b has come..

oh forgot to mention, its impossible to explain the manager that nightly today is the same as Rc3. no technical background what so ever. more like if(strstr("*version*","RC")) return ok else return not ok..

[byo]

For me it is. my "quality manager" will not let me upgrade my building machine unless its a final or a RC..
so at the moment I am using the nightly and have rc2 on the build...
problem is that I can not open the project files with that rc2 made with the nightly.
so from time to time i need to use the rc2..

is does give you a good impression in how far c::b has come..

oh forgot to mention, its impossible to explain the manager that nightly today is the same as Rc3. no technical background what so ever. more like if(strstr("*version*","RC")) return ok else return not ok..

I agree that "Stable" release may be really important from business point of view. And after stable release, the interest in project may be much bigger - information about such release comes to more people, download servers put it into it's websites and much more.

But on the other hand if we have some delay and still there are people waiting for C::B it leads to the conclusion that people want C::B because of it's quality and/or capabilities, not because there's CURRENTLY no alternative. That looks promising

But I hoope that we will reach RC3 soon (even though I can use nightlies and there's much work to do I just can't wait )