string freeze policy and release notes

[Matthew Miller]

Okay, so, someone asked me about the freeze and how that relates to
release notes.

I found

https://fedoraproject.org/wiki/Release_notes_process#The_Process

which seems basically sane. But I also found

http://fedoraproject.org/wiki/L10N_Freezes#What_changes_are_affected_by_t...

which states explicitly that it convers release notes, and gives an
exception policy here:

https://fedoraproject.org/wiki/Software_String_Freeze_Policy

which also doesn't sound completely off base, except that the string
freeze is nominally at the same time as the *alpha* freeze, which seems
significantly early (halfway through the six month release cycle) for
meaningful release notes.

What's the deal here — is some of this out of date and due for a
revision?

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Pete Travis]

On May 13, 2015 1:25 PM, "Matthew Miller" <mattdm(a)fedoraproject.org&gt;
wrote:
>  Okay, so, someone asked me about the freeze and how that relates to
>  release notes.
>
>  I found
>
>  https://fedoraproject.org/wiki/Release_notes_process#The_Process
>
>  which seems basically sane. But I also found
http://fedoraproject.org/wiki/L10N_Freezes#What_changes_are_affected_by_t...
>  which states explicitly that it convers release notes, and gives an
>  exception policy here:
>
>  https://fedoraproject.org/wiki/Software_String_Freeze_Policy
>
>  which also doesn't sound completely off base, except that the string
>  freeze is nominally at the same time as the *alpha* freeze, which seems
>  significantly early (halfway through the six month release cycle) for
>  meaningful release notes.
>
>  What's the deal here — is some of this out of date and due for a
>  revision?
>
>  --
>  Matthew Miller
>  <mattdm(a)fedoraproject.org&gt;
>  Fedora Project Leader
>  -- 
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.

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.

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.

Also, yes, many docs contributor facing wiki pages are stale.  It's on a
list...

HTH,

--Pete

[Matthew Miller]

On Wed, May 13, 2015 at 01:45:59PM -0600, Pete Travis wrote:
>  Also, yes, many docs contributor facing wiki pages are stale. 
> It's on a
>  list... 
Not just docs. :) Thanks for the updates.


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Leslie S Satenstein]

I have been pleased with the Fedora wiki and the ability to correct documentation that is
in error.  
Perhaps its time to look at the fedora wiki style of document maintenance. I see that it
works for the wiki, it could very well work for the docs project.  It works so well that
it should serve for a new paradigm. Put the F22 docs on the wiki and allow authorized FAS
user to perform updates. The approvals would still come from Petes group.  

For Fedora 23, do put all the documents on a documents wiki. 

The users and developers can do justice to what is provided in the form of updates. FAS
members can correct or add to the docs. Of course, updates still have to be vetted, but at
least, no docbook or publican, which is a chore alone. The release notes and other docs
are out of date. For F22, Yum is king. etc. dnf is not even a prince. 


 Regards 
 Leslie
 Mr. Leslie Satenstein
Montréal Québec, Canada


 
      From: Matthew Miller <mattdm(a)fedoraproject.org&gt;
 To: docs(a)lists.fedoraproject.org; trans(a)lists.fedoraproject.org 
 Sent: Wednesday, May 13, 2015 3:25 PM
 Subject: string freeze policy and release notes
   
Okay, so, someone asked me about the freeze and how that relates to
release notes.

I found

https://fedoraproject.org/wiki/Release_notes_process#The_Process

which seems basically sane. But I also found

http://fedoraproject.org/wiki/L10N_Freezes#What_changes_are_affected_by_t...

which states explicitly that it convers release notes, and gives an
exception policy here:

https://fedoraproject.org/wiki/Software_String_Freeze_Policy

which also doesn't sound completely off base, except that the string
freeze is nominally at the same time as the *alpha* freeze, which seems
significantly early (halfway through the six month release cycle) for
meaningful release notes.

What's the deal here — is some of this out of date and due for a
revision?

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader
-- 
docs mailing list
docs(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs