Re: Tasks remaining for 2.16 release?
2012/1/26 Graham Percival : >> 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 better 2014. Jokes aside, please allow some time for us to do our work. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tasks remaining for 2.16 release?
2012/1/26 David Kastrup : > 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 > strictly speaking depends on everything else being frozen, but some > overlap should be tolerable. Yes as long as we have 1-2 weeks to finish everything after the rest is finished. If plans to release include forking the stable branch, I would like that also the translation branch is forked at the same time. Otherwise it is nearly unmanageable. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Tasks remaining for 2.16 release?
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 for obvious mistakes no, we've never bothered with that in the past, and this would push the release back to summer or later > e) make sure all appropriate regtests are there no, we've never bothered with that in the past, and this would push the release back to summer or later > f) update the snippets for stuff that could now be done easier no, we've never bothered with that in the past, and this would push the release back to summer or later > g) get the translations up to par where there are translation workers no, we've never bothered with that in the past, and this would push the release back to 2013 or later > h) release. yes I'd be tempted to add "update LSR to 2.14", but: a) that's not likely to happen due to lack of interest amongst active users (this isn't a developer-only task!) b) we've never bothered with that before - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Tasks remaining for 2.16 release?
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 stuff that could now be done easier g) get the translations up to par where there are translation workers h) release. As far as I can see, the snippet _code_ is not subject to translation issues, so e) can be pretty much done in parallel. Translation work strictly speaking depends on everything else being frozen, but some overlap should be tolerable. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
