I am interesting in helping with the testing effort for CKeditor 3.0. This would include submitting bug reports with patches. My question is, when is it worth starting to do this? I don't want to start so early in the process that the fixes have a high probability of being broken again, but I don't want to start so late that it's too late to get them into 3.0.
On a related note, is there any sort of timetable for new betas/release candidates/final release? I'm not asking for firm dates, just a general estimate.
On a related note, is there any sort of timetable for new betas/release candidates/final release? I'm not asking for firm dates, just a general estimate.
Re: When to do QA
As I said, look at the known bugs, maybe you might spend a lot of time researching for something that it's already known. Also looking at them you might understand easier the way that tickets are handled.
Re: When to do QA
This is exactly the right moment for it, and your help is definitely welcome.
We are now on the stabilization phase of the editor. We'll not have further betas. The next release will be our (first?!) RC. Actually, the RC should not be that far. We'll have it as soon as we have all critical bugs fixed, and when all browser compatibility issues are fixed (we have more serious issues with FF2 and IE8 right now).
We don't have precise dates. We would like to have the RC asap. The final release will come out as soon as we have all targeted tickets fixed. So, the best way to understand the status of it is by following the milestone page:
http://dev.fckeditor.net/milestone/CKEditor%203.0
I look forward to seeing you at our ticketing system. Thanks!
Fred
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn