Vincent van Ravesteijn wrote: > >> - Will there be a code-freeze after that strings can still be changed? > > > > Is this what is normally done? I'm new at this. > > I've actually no clue what is meant with a code freeze after that > strings an be changed ?
I think the question was, whether the feature freeze includes string freeze or there will be separate one. This question is relevant to both docs and translators because if we continuously change the translatable strings they can't reasonably work. My approach to this used to be: 1. summarize all features people want to finish and most critical bugs to be solved for release. 2. based on feelings from (1) announce some time schedule for alpha/beta/rc (yes, it will be broken but people can synchronize much better when some time plan is announced) 3. releasing alphas until features are done or kicked away (or some critical bugs). then soft freeze - no more new features, people should focus on fixing bugs. it's also time to freeze the strings so translators and documentation can be done - time to send some suppliant mail to trnaslators & doclist. 4. release beta. if no major bugs found and some reasonable time for testing by users was provided go to rc, if no continue with next betas. 5. rc, hard freeze. every commit needs either release manager or two devs ack, only docs and translation can still flow in. So back to Uwe's question, it would be good you announce at some point - features won't change ( except of bugfixing ) - translatable strings are not going to be changed (except obvious bugs/typos). and maybe give some hint when this might occur :) YMMV, Pavel
