hi, time to think about beta3. there is already a couple of things which need to be released and tested so we should start freezing at certain time.
are there some particular issues you want to push in trunk before next beta? we reduced from 3 pages of bugs with 2.0 milestone to nearly one page at my screen ;) thats the good part. the bad part is that the top critical/major issues are pretty constant. since there are no signs this will change soon their occurence is probably not good indicator for switching to rc1 if we want to release some day. or should we devote one release cycle only to them? because rc should be almost final shape there are few things i would like to know for the planning: - rc2rc conversion. some basic was put together by Richard. is anybody planning to work upon it? - windows installers. Joost, are there some advances in the announced 'joint' installer, so we no more proceed with the doublet official/alternative? or do we continue with the current 1.6 model? any way we should start to offer *some* official installer in case you plan to continue contributing it. - documentation. Uwe, do you have some expectation about the time you need/want, so the docs are in good shape in your view? especially the first two issues should have clear answer before rc, since its imho too late to debug all the bugs around oncewe enter rc1 imho. other things, proposals? pavel
