[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: RFC Change Documentation Freeze in Release Schedule
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2011-12-05 18:02:03
Message-ID: 1773241.YClnrCTkU6 () xps
[Download RAW message or body]

El Dilluns, 5 de desembre de 2011, a les 09:58:56, Burkhard Lück va escriure:
> Am Montag, 5. Dezember 2011, 00:02:18 schrieb Albert Astals Cid:
> > El Diumenge, 4 de desembre de 2011, a les 23:51:27, Burkhard Lück va
> 
> escriure:
> > > Am Samstag, 3. Dezember 2011, 14:41:10 schrieb Burkhard Lück:
> > > > Hi Translators,
> > > > 
> > > > our release schedules actually have these dates regarding
> > > > Gui/Doc
> > > > string freeze:
> > > > 
> > > > Soft Message Freeze (2011-11-10)  ~10 weeks until Final Tag
> > > > (2012-01-18) Documentation Freeze (2011-11-28) ~7 weeks until
> > > > Final
> > > > Tag (2012-01-18) Hard Message Freeze (2011-12-19) ~ 4 weeks
> > > > until
> > > > Final Tag (2012-01-18)
> > > > 
> > > > I propose to move the Documentation Freeze date 3 weeks later to
> > > > the
> > > > Hard
> > > > Message Freeze date, then we have 4 weeks until the Final Tag.
> > > > 
> > > > Reason for that move:
> > > > 
> > > > 1) Due to the regular doc backports from master/trunk once a
> > > > month with up to 1000 new/changed doc strings in minor releases
> > > > the amount of new/changed doc strings before a major release
> > > > ist not so much, that we need 7 weeks. That is at least my
> > > > experience in the german translation team.
> > > > 
> > > > 2) Doc backport policy allows backport of doc changes from trunk
> > > > in the week after each minor release. In this case that means,
> > > > teams will translate wrong docs (e.g. gwenview/rocs) now, but
> > > > have to retranslate that after the next backport for 4.8.1.
> > > > From my pov this is just a waste of team ressources, especially
> > > > for smaler teams.
> > > > 
> > > > What do you think about this proposal?
> > > 
> > > Hmm... the Unix way to answer - no news is good news?
> > 
> > I guess :D
> > 
> > You know you have to change the schedule generator program so that the
> > next we autogenerate includes those changes?
> 
> Yes.
> 
> And I'd like to change the description for Documentation Freeze:
> 
> case docfreeze :
> -  desc = "No more substantive changes to documentation or handbooks "
> -             "after this date. Typos, spelling and simple grammar changes "
> -             "are permitted.";
> + desc = "No more changes to documentation or handbooks after this date. "
> +           "For typos, spelling and simple grammar changes you have to mail
> " +           "kde-i18n-doc for approval.";
> 
> Then it is similar to the description for hard message freeze.

Ok for me.

Albert
[prev in list] [next in list] [prev in thread] [next in thread]