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
http://dev.fckeditor.net/milestone/CKEditor%203.0
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn