<p dir="ltr"><br>
On May 13, 2015 1:25 PM, "Matthew Miller" <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>> wrote:<br>
><br>
> Okay, so, someone asked me about the freeze and how that relates to<br>
> release notes.<br>
><br>
> I found<br>
><br>
> <a href="https://fedoraproject.org/wiki/Release_notes_process#The_Process">https://fedoraproject.org/wiki/Release_notes_process#The_Process</a><br>
><br>
> which seems basically sane. But I also found<br>
><br>
> <a href="http://fedoraproject.org/wiki/L10N_Freezes#What_changes_are_affected_by_the_string_freeze.3F">http://fedoraproject.org/wiki/L10N_Freezes#What_changes_are_affected_by_the_string_freeze.3F</a><br>
><br>
> which states explicitly that it convers release notes, and gives an<br>
> exception policy here:<br>
><br>
> <a href="https://fedoraproject.org/wiki/Software_String_Freeze_Policy">https://fedoraproject.org/wiki/Software_String_Freeze_Policy</a><br>
><br>
> which also doesn't sound completely off base, except that the string<br>
> freeze is nominally at the same time as the *alpha* freeze, which seems<br>
> significantly early (halfway through the six month release cycle) for<br>
> meaningful release notes.<br>
><br>
> What's the deal here — is some of this out of date and due for a<br>
> revision?<br>
><br>
> --<br>
> Matthew Miller<br>
> <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>
> Fedora Project Leader<br>
> --<br></p>
<p dir="ltr">We've been quite lax about this. The best resource is probably the docs tasks schedule maintained by jreznik, but in a practical sense, we work on RNs until we're burned out on them, without really honoring a 'freeze'. It's probably not the best approach, but it is a best-effort strategy that makes good use of limited volunteer cycles. As you say, things happen or are discovered late in the cycle that we want to cover.</p>
<p dir="ltr">The translation teams have been very good about jumping on POTs when they're pushed out (and yes, that needs to be refreshed ASAP, sorry). Docs stops pulling strings and publishing translations when the translation teams stop asking us to - no formal hard stop is enforced, except perhaps a release EOL. Otherwise, a bz ticket or IRC poke or whatever makes it happen; some teams even publish themselves.</p>
<p dir="ltr">The one thing people really have to watch for is the wiki freeze, around Beta release day. Once we start final markup, it's more work to monitor and maintain continuity between content in two places.</p>
<p dir="ltr">Also, yes, many docs contributor facing wiki pages are stale. It's on a list...</p>
<p dir="ltr">HTH,</p>
<p dir="ltr">--Pete</p>