Re: Current state of release planning.

[David Kastrup]

John Mandereau <address@hidden> writes:

> Le dimanche 12 août 2012 à 14:48 +0200, David Kastrup a écrit :
>> Documentation improvements are still admissable, documentation rewrites
>> not necessarily as we want to avoid significant changes between the
>> English documentation and reasonably well-maintained translations.  I
>> have no clear view regarding finalizing of the translations.
>
> As long as no documentation significant rewrite reaches master,
> finalizing translations of the documentation may be done by
> cherry-picking commits from translation branch; would you like to do
> or delegate this?

I haven't really tracked translations so far, so my own level of
suitability here is pretty close to zero, modulo non-task-specific
computer expertise (which some people deem sufficient for making me
useful for Windows support, a system I have successfully avoided for
decades).  In other words, I'd be happy to delegate, but we are not
likely to have the help of patchy-staging for it.  Stuff has to be
well-tested.

> On the contrary, if big doc changes reach master before 2.16.0 is out,
> a new branch translation-2.16 should be created, that would be merged
> into and from stable/2.16 the same way as translation and
> master/staging, with some extra care deserved by stable/2.16; if there
> is the need for it, I could handle this, having in mind that checking
> "make dist" is currently a PIOA (i.e. a pain for all of us).
>
> I've sent an update request to the Translation Project with 2.15.95
> release (with address@hidden in CC), so within a week we
> should get numbers of PO files to check in in master and stable/2.16.

I am clueless in that area, so it will be good if you kept track of what
was required here.  I think we have a reasonable chance to be in the
same room with Graham when releasing 2.16 if things go well.

-- 
David Kastrup