Pavel Sanda wrote: > thus i plan release candidate 1 around 7. march. few more notes: i would like to make soft freeze one week before, in order to avoid needless regressions. (RC is most probaly going to reach more linux repos and users and it should mean what is says - candidate for release.)
as usually doc/translation can go in but i will be far less inclined to accept patches except 'fix for bug #xxx'. this should hold also for RC development stage. some day at this stage i want to make translation strings freeze and ask translators last time... the number of new 2.0 bug reports seems to be low so i dont plan to repeat 6 RCs like for the 1.6.0. to my surprise win installer code started to move. Joost, do you have some private estimation what time is needed to finish your changes so installer could be published? also do you think some code inside src/ needs to be touched for the new dictionary stuff? to sum up if you have some necessary code for 2.0, there is not much time left. pavel
