Well, here is what I can think off my head.
a) feature freeze. Nothing added that requires documentation changes.
b) get rid of all critical issues
c) release candidate(s)
d) proofread the docs for obvious mistakes
e) make sure all appropriate regtests are there
f) update the snippets for
On Thu, Jan 26, 2012 at 12:33:31PM +0100, David Kastrup wrote:
a) feature freeze. Nothing added that requires documentation changes.
why bother? the two-week release candidate takes care of this.
b) get rid of all critical issues
yes
c) release candidate(s)
yes
d) proofread the docs
2012/1/26 David Kastrup d...@gnu.org:
As far as I can see, the snippet _code_ is not subject to translation
issues,
Right. Just make sure any _needed_ (backwards-incompatible) change in
code is made in translations as well.
so e) can be pretty much done in parallel. Translation work
2012/1/26 Graham Percival gra...@percival-music.ca:
g) get the translations up to par where there are translation workers
no,
Yes
we've never bothered with that in the past,
_we_ have actuall bothered.
and this would
push the release back to 2013 or later
Don't underestimate us. Say
