just added

[bpratt]

BeNe Wrote:What about a RC4 Branch ?
So raphael can spend his time to new features and the other can bring RC3 to the end. The time we loose so is not more so much.

If RC3 isn't going to make it full release, then I agree that you need to get RC3 out the door to the masses, and start work on a RC4. As that way you will have a whole lot more people up to a common version where they won't be whinging about ancient bugs from RC2c anymore !


Once you have people up to RC3, then you remind them that the nightly builds are available and can be done without too many problems.


I think that I am like many others who started with RC2c, and thought that RC3 was very close by, so did not bother with the incremental nightly updates, with the thinking of "why bother when RC3 is just around the corner", and now with such a huge manual job to update their RC2c to a current nightly build, they are less likely to spend the huge amount of time to do that.


I also think we all know that RC3 is not going to be the one before Version 1.0 , so perhaps it really is time to get RC3 out the door as it is, with a complete listing of the change requirements for those on RC2c (that's if there's no update script available).

That way you guys can get a start on RC4, and in the mean time you'll get a lot more people up to much more recent and a whole lot more relevant version of RC3.

I speak for myself, but I would not be totally surprised if many others agree with me, when I say I don't really care if we end up doing a couple more Release Candidates before Version 1.0 is released.

I think having long delays between Release Candidates is really hurting not only the development, but the credibility of this project, as it appears from an outsiders perspective to be a stagnant project. People need to see things happening, and to the public, RC2c was the latest thing !