Re: Todo list for the release notes
Hi,
After a quick discussion with Martin, Javier, Simon and Francois, we
assembled this todo-list, for the Squeeze release (target for April).
On Wed, 2009-07-29 at 13:52 +0200, Nicolas François wrote:
> On Wed, Jul 29, 2009 at 10:30:30AM +0200, fpiat@klabs.be wrote:
> >
> > * The docbook XSL lacks some translations and/or doesn't support some
> > languages (for some standards strings, like "Table of contents").
> > * Turn the Release notes into a package (for build dependencies...)
> > * Script to fetch release figures from UDD (number of developers,
> > number of packages...)
> > note: compiling the packages should not modify the package and
> > must not require network.
> > * Parallel building should work, needs testing.
> > * Remove the workaround for old version of some tools (Po4A, dblatex,
> > xmlroff)
>
> Also update the material based on those files (e.g. PO files)
>
> > * Drop xmlroff if possible (for be ja ml pl vi zh_CN zh_TW)
> > * Try to convince the remaining full text translators (ca cs pt_BR) to
> > use Po4a instead of plain text.
>
> After talking to Felipe, pt_BR really want to keep the xml format
> translation process.
>
> > * TBC: po4a didn't return the right exit code, implied non-necessary
> > po4a run by the past
>
> I will check
> Also: add an option to continue after a failure (but still fail at the
> end)
>
> > * use on single po4a file for many xml files
> > * test if it more performant
> > - prevent parallelization of translation in large teams?
> > - allow to move 1 paragraph to another page
>
> We need to talk to debian-i18n for this, and stress out the advantages.
>
> Check if the teams share the load, explain how they can do it with a
> single PO file.
>
> > Time frame:
> > Until the freeze, we can improve and fix the build system.
> > Once the freeze starts, we can start working on the R.Notes.
>
> Announce a schedule.
> Frreze the R.N. toolchain (and announce the freeze)
>
> Find the report from JFS on what he did for the R.N.
>
> Testing can start after the freeze according to JFS
>
> We need to register to the pseudo-package "upgrade-reports"
>
> Prepare the infrastructure for testing (i.e. how to split the tests among
> testers)
> JFS performed tests based on tasksel installation
Reply to: