User forums > General (but related to Code::Blocks)

Release Early, Release Often

<< < (2/4) > >>

batwings:
MISSION:RC3-IMPOSSIBLE

What is preventing us from challenge it?
No doubt, any nightly build now is reaching the goals of RC3 milestone.

It is the time for team to spend a little bit time to make a RC3 release.

DC@DR:
Yes, I strongly agree that we should "release more, release often". It's true that many users won't bother to see what's going on with the nightly builds, and when they find out that the RC2 stays there for approx. 1 year, they will surely assume that the project has gone to an end/death, then they just move on without thinking about a return visit. That's sad, devs, since we need more users, we need to spread the word, that's the idea of open source community to fight for right to exist in the contemporary commercial universe :)

kidmosey:

--- Quote from: BigAngryDog on November 23, 2006, 02:10:20 pm ---90% of visitors will see the web site home page and never bother with a nightly.

--- End quote ---

where do you get this statistic?


When I went to download, I saw on the page where it said many of the nightlies are as much or more stable than RC2, so I downloaded a nightly.  Maybe this puts me among the "10% of visitors" that doesn't care about the postfix on an application name, but about the application functionality.

bertg:

--- Quote from: kidmosey on November 24, 2006, 07:50:56 am ---When I went to download, I saw on the page where it said many of the nightlies are as much or more stable than RC2, so I downloaded a nightly.  Maybe this puts me among the "10% of visitors" that doesn't care about the postfix on an application name, but about the application functionality.

--- End quote ---

There's more to it than just a postfix on a filename. When you use a nightly build, you volunteer to test out bleeding edge code that has been introduced into the project <24hrs ago. And that is a good thing. After all, many volunteer testers make a free software project work.

But there are also people, like me, who don't have the guts or the time to use untested releases. For these people a release branch where the only expected changes are bugfixes would be great. My bet is that the number of people who are genuinely interested in CodeBlocks - but too squeamish to get involved in testing - is an order of magnitude greater than the number of people actively testing.

Right now, the project finds itself in a loop between the developers and a group of "hardcore" alpha testers. If a relatively stable release could be spun every 6 months or so, CodeBlocks would find its way to a much larger user community. More testers, developers and plugin writers could trickle down from this community to give the project a helping hand. It's up to the core developers to decide if that kind of exposure is desirable at this stage.

BrianSidebotham:
I don't visit the forums for the nightly builds, in fact I rarely visit the forums! :( I start the day with a cup of tea and "svn update" to see what's changed. I can normally tell by whats updated whether it's worth a re-compile or not.

I actually quite like the system, and the nightly builds are not what I would class as unstable at all. For a few people mainly working on the project, there is on average an update per day and you can't ask for more than that.

As for the comments about turning code completion off, I answer with WHAT!? That imo is pretty much c::b's most powerful feature. It's pretty much the single reason I use it. c::b isn't geared towards embedded C development, but the code completion is much better than in any other open source ide. I really get on with it. If you took that out, I'd go back to programmers notepad.

I don't see why people are so desperate to see a current nightly build labeled RC3. Just use a nightly build and have done!

Navigation

[0] Message Index

[#] Next page

[*] Previous page