[openstack-dev] Need for a String Freeze for documenters/translators
anne at openstack.org
Fri Jan 25 15:58:54 UTC 2013
On Fri, Jan 25, 2013 at 8:33 AM, Thierry Carrez <thierry at openstack.org>wrote:
> Mark McLoughlin wrote:
> > I agree with it in principal. I think complete translations are
> > important and the only way to achieve that at release time is to stop
> > changing them soon enough to give translators a reasonable chance to do
> > their thing.
> Note that this is not just about translation, but also about
> documentation. It's difficult to write doc when error messages or option
> names continue to change until the last minute.
Yes, this does help, but does not make docs more complete or easier to
finish sooner on its own. We've still got 20+ undocumented Grizzly features
that we're tracking (10+ more possibilities that haven't landed in code).
 For all the releases so far, we haven't simultaneously released
documentation since it just wasn't nearly complete enough.
Also want to raise my hand and say a doc freeze for translations must be
separate from this code string freeze.
Now hungry for some ice cream,
> > [...]
> > Finally, if there's a string freeze then there also needs to be a
> > process for approving freeze breaks. Sometimes you can't fix a serious
> > bug without changing a string and that has to be allowed.
> Yes, all freezes come with an exception procedure. It can be as simple
> as sending an email to the list, or requiring a comment on a bug. The
> goal is to make sure we make user-visible changes for a good reason, and
> that all the downstream stakeholders are aware of that particular
> Thierry Carrez (ttx)
> Release Manager, OpenStack
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev