Re: Fedora 35 release notes are now open!

Sarah Finn <[email protected]> Tue, 12 Oct 2021 17:25:02 +0100
Newsgroups gmane.linux.redhat.fedora.documentation
Message-ID <CAOWyT990nG=WjyJib0AFSBcogDD58uggv0fCCFqCp8SOAm3FoQ@mail.gmail.com>
--===============6978339917730445470==
Content-Type: multipart/alternative; boundary="0000000000003ef22705ce2a4a39"

--0000000000003ef22705ce2a4a39
Content-Type: text/plain; charset="UTF-8"

Great stuff Petr!

On Thu, 7 Oct 2021 at 21:26, Petr Bokoc <[email protected]> wrote:

> Hi everyone,
>
> Fedora 35 Beta is out now[0], so it's time to start writing release notes
> once again!
>
> As usual, we aim to cover notable Changes[1]. Ben Cotton has been tracking
> those in our release-notes issues for us, which allows us to grab a list of
> everything that needs to be documented[2]. Branch *f35* is ready for your
> pull requests.
>
> = What to do
>
> 1. Pick one or more issues in the list linked above.
>
> 2. Open each issue you picked, and click the Take button on the right to
> claim it. (If you claim an issue but later find out you don't have time to
> write about it, remove yourself from the issue ASAP so others can see it's
> free and take it!)
>
> 3. Find some information about the issue. A lot of them have plenty of
> info in them already; if not, find out who's responsible for the change,
> and talk to them on IRC or via mail. Of course it's always better if you
> try to do research before you ask questions. Note that you might not always
> be able to reach the owner in a reasonable timeframe; in that case just do
> your best, I'll be reviewing PRs, so if we publish something wrong, it's on
> me.
>
> 4. Write a release note about the issue. If you're not sure how exactly a
> release note looks, check out some of the previous releases for
> inspiration. We don't want any long, overly technical texts, the release
> notes are generally meant to highlight changes, not to tell people how to
> use something.
>
> 5. Now the workflow diverges based on your permissions and technical
> skills:
>
>     5a. If you know how to use git and asciidoc, we'd appreciate it if you
> wrote up the release note and sent a pull request against the main repo,
> branch "f35". Your contributions should go into one of the files in
> "modules/release-notes/pages/", which one exactly depends on the contents
> of the change you're documenting. Use the "build.sh" and "preview.sh"
> scripts in the repository root to preview your changes locally; see the
> repository README for specific instructions. If you can't see the section
> where you added your contributions at all, make sure it's included in
> "modules/release-notes/nav.adoc".
>
>     5b. If the above sounds like gibberish to you, it's fine: just add a
> comment with your text into the issue, and ping me on IRC/Telegram/Matrix
> or through e-mail[3]; I'll mark it up for you and make sure your
> contribution appears in the final document.
>
> See also our contributor docs[4] for some additional info and tips;
> especially the "Git for docs writers" section if you're not familiar with
> the system.
>
> If anyone has any questions, go ahead and ask either here on the list or
> on IRC, I'm happy to help. The current schedule shows the preferred final
> release target on *October 19*, which gives us about 2 weeks to work with,
> which really isn't much. The release date may slip, but don't count on it.
>
> Happy writing!
>
> Petr
>
> [0] https://fedoramagazine.org/announcing-fedora-35-beta/
> [1] https://fedoraproject.org/wiki/Releases/35/ChangeSet
> [2]
> https://pagure.io/fedora-docs/release-notes/issues?status=Open&search_pattern=F35&close_status=
> [3] https://docs.fedoraproject.org/en-US/fedora-docs/#find-docs
> [4] https://docs.fedoraproject.org/en-US/fedora-docs/
> _______________________________________________
> docs mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 

Sarah Finn

She/Her

Senior Agile Practitioner

Agile DevOps CoP Manager

Red Hat <https://www.redhat.com/>

Waterford, Ireland

[email protected]
M: 0879830832
@RedHat <https://twitter.com/redhat>   Red Hat
<https://www.linkedin.com/company/red-hat>  Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.redhat.com/>

*"If you are not willing to risk the usual, you will have to settle for the
ordinary."*

--0000000000003ef22705ce2a4a39
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Great stuff Petr!=C2=A0</div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 7 Oct 2021 at 21:26, Petr B=
okoc &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"=
ltr">Hi everyone,<br>
<br>
Fedora 35 Beta is out now[0], so it&#39;s time to start writing release not=
es once again!<br>
<br>
As usual, we aim to cover notable Changes[1]. Ben Cotton has been=20
tracking those in our release-notes issues for us, which allows us to=20
grab a list of everything that needs to be documented[2]. Branch *f35*=20
is ready for your pull requests.<br>
<br>
=3D What to do<br>
<br>
1. Pick one or more issues in the list linked above.<br>
<br>
2. Open each issue you picked, and click the Take button on the right to
 claim it. (If you claim an issue but later find out you don&#39;t have tim=
e
 to write about it, remove yourself from the issue ASAP so others can=20
see it&#39;s free and take it!)<br>
<br>
3. Find some information about the issue. A lot of them have plenty of=20
info in them already; if not, find out who&#39;s responsible for the change=
,
 and talk to them on IRC or via mail. Of course it&#39;s always better if=
=20
you try to do research before you ask questions. Note that you might not
 always be able to reach the owner in a reasonable timeframe; in that=20
case just do your best, I&#39;ll be reviewing PRs, so if we publish=20
something wrong, it&#39;s on me.<br>
<br>
4. Write a release note about the issue. If you&#39;re not sure how exactly=
 a
 release note looks, check out some of the previous releases for=20
inspiration. We don&#39;t want any long, overly technical texts, the releas=
e
 notes are generally meant to highlight changes, not to tell people how=20
to use something.<br>
<br>
5. Now the workflow diverges based on your permissions and technical skills=
:=C2=A0=C2=A0<br>
<br>
=C2=A0=C2=A0=C2=A0 5a. If you know how to use git and asciidoc, we&#39;d ap=
preciate it if you=20
wrote up the release note and sent a pull request against the main repo,
 branch &quot;f35&quot;. Your contributions should go into one of the files=
 in=20
&quot;modules/release-notes/pages/&quot;, which one exactly depends on the=
=20
contents of the change you&#39;re documenting. Use the &quot;build.sh&quot;=
 and=20
&quot;preview.sh&quot; scripts in the repository root to preview your chang=
es=20
locally; see the repository README for specific instructions. If you=20
can&#39;t see the section where you added your contributions at all, make=
=20
sure it&#39;s included in &quot;modules/release-notes/nav.adoc&quot;.<br>
<br>
=C2=A0=C2=A0=C2=A0 5b. If the above sounds like gibberish to you, it&#39;s =
fine: just add a
 comment with your text into the issue, and ping me on IRC/Telegram/Matrix =
or=20
through e-mail[3]; I&#39;ll mark it up for you and make sure your=20
contribution appears in the final document.<br>
<br>
See also our contributor docs[4] for some additional info and tips;=20
especially the &quot;Git for docs writers&quot; section if you&#39;re not f=
amiliar=20
with the system.<br>
<br>
If anyone has any questions, go ahead and ask either here on the list or
 on IRC, I&#39;m happy to help. The current schedule shows the preferred=20
final release target on *October 19*, which gives us about 2 weeks to work =
with, which really isn&#39;t much. The release date may slip, but don&#39;t=
 count on it.<br>
<br>
Happy writing!<br>
<br>
Petr<br>
<br>
[0] <a href=3D"https://fedoramagazine.org/announcing-fedora-35-beta/" targe=
t=3D"_blank">https://fedoramagazine.org/announcing-fedora-35-beta/</a><br>
[1] <a href=3D"https://fedoraproject.org/wiki/Releases/35/ChangeSet" target=
=3D"_blank">https://fedoraproject.org/wiki/Releases/35/ChangeSet</a><br>
[2] <a href=3D"https://pagure.io/fedora-docs/release-notes/issues?status=3D=
Open&amp;search_pattern=3DF35&amp;close_status=3D" target=3D"_blank">https:=
//pagure.io/fedora-docs/release-notes/issues?status=3DOpen&amp;search_patte=
rn=3DF35&amp;close_status=3D</a><br>
[3] <a href=3D"https://docs.fedoraproject.org/en-US/fedora-docs/#find-docs"=
 rel=3D"noreferrer" target=3D"_blank">https://docs.fedoraproject.org/en-US/=
fedora-docs/#find-docs</a> <br>[4] <a href=3D"https://docs.fedoraproject.or=
g/en-US/fedora-docs/" rel=3D"noreferrer" target=3D"_blank">https://docs.fed=
oraproject.org/en-US/fedora-docs/</a></div>
_______________________________________________<br>
docs mailing list -- <a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]=
oject.org" target=3D"_blank">[email protected]</a><br>
Fedora Code of Conduct: <a href=3D"https://docs.fedoraproject.org/en-US/pro=
ject/code-of-conduct/" rel=3D"noreferrer" target=3D"_blank">https://docs.fe=
doraproject.org/en-US/project/code-of-conduct/</a><br>
List Guidelines: <a href=3D"https://fedoraproject.org/wiki/Mailing_list_gui=
delines" rel=3D"noreferrer" target=3D"_blank">https://fedoraproject.org/wik=
i/Mailing_list_guidelines</a><br>
List Archives: <a href=3D"https://lists.fedoraproject.org/archives/list/doc=
[email protected]" rel=3D"noreferrer" target=3D"_blank">https://lis=
ts.fedoraproject.org/archives/list/[email protected]</a><br>
Do not reply to spam on the list, report it: <a href=3D"https://pagure.io/f=
edora-infrastructure" rel=3D"noreferrer" target=3D"_blank">https://pagure.i=
o/fedora-infrastructure</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><p style=3D"color:rgb(0,0,0);font-family:RedHatText,san=
s-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px"><span>Sarah=
</span>=C2=A0<span>Finn</span><span style=3D"text-transform:uppercase;color=
:rgb(170,170,170);margin:0px"></span></p><p style=3D"color:rgb(0,0,0);font-=
family:RedHatText,sans-serif;font-size:12px;margin:0px 0px 4px;text-transfo=
rm:capitalize">She/Her</p><p style=3D"color:rgb(0,0,0);font-family:RedHatTe=
xt,sans-serif;font-size:12px;margin:0px"><span>Senior Agile Practitioner</s=
pan></p><p style=3D"color:rgb(0,0,0);font-family:RedHatText,sans-serif;font=
-size:12px;margin:0px">Agile DevOps CoP Manager<span><br></span></p><p styl=
e=3D"color:rgb(0,0,0);font-family:RedHatText,sans-serif;margin:0px 0px 4px;=
font-size:12px"><a href=3D"https://www.redhat.com/" style=3D"color:rgb(0,13=
6,206);margin:0px" target=3D"_blank">Red Hat</a></p><div style=3D"color:rgb=
(0,0,0);font-family:RedHatText,sans-serif;font-size:medium;margin-bottom:4p=
x"><span><p style=3D"font-size:12px;margin:0px">Waterford, Ireland</p></spa=
n></div><p style=3D"color:rgb(0,0,0);font-family:RedHatText,sans-serif;marg=
in:0px;font-size:12px"><span style=3D"margin:0px;padding:0px"><a href=3D"ma=
ilto:[email protected]" style=3D"color:rgb(0,0,0);margin:0px" target=3D"_bla=
nk">[email protected]</a>=C2=A0 =C2=A0</span><span><br>M:=C2=A0<a href=3D"te=
l:0879830832" style=3D"color:rgb(0,0,0);margin:0px" target=3D"_blank">08798=
30832</a>=C2=A0=C2=A0 =C2=A0</span></p><div style=3D"color:rgb(0,0,0);font-=
family:RedHatText,sans-serif;font-size:12px;margin-bottom:8px"><div><a href=
=3D"https://twitter.com/redhat" title=3D"twitter" style=3D"background:url(&=
quot;https://static.redhat.com/libs/redhat/brand-assets/2/social/social-med=
ia--twitter--53x53.png&quot;) 0px 50%/14px no-repeat transparent;color:rgb(=
0,0,0);display:inline-block;line-height:20px;padding-left:14px" target=3D"_=
blank"><span style=3D"margin-left:2px">@RedHat</span></a>=C2=A0=C2=A0=C2=A0=
<a href=3D"https://www.linkedin.com/company/red-hat" title=3D"LinkedIn" sty=
le=3D"background:url(&quot;https://static.redhat.com/libs/redhat/brand-asse=
ts/2/social/social-media--linkedin--53x46.png&quot;) 0px 50%/14px no-repeat=
 transparent;color:rgb(0,0,0);display:inline-block;line-height:20px;padding=
-left:14px;margin:0px 4px 0px 3px;padding-top:1px" target=3D"_blank"><span =
style=3D"margin-left:4px">Red Hat</span></a>=C2=A0=C2=A0<a href=3D"https://=
www.facebook.com/RedHatInc" title=3D"Facebook" style=3D"background:url(&quo=
t;https://static.redhat.com/libs/redhat/brand-assets/2/social/social-media-=
-facebook--53x13.png&quot;) 0px 50%/9px no-repeat transparent;color:rgb(0,0=
,0);display:inline-block;line-height:20px;padding-left:12px;padding-top:1px=
" target=3D"_blank"><span>Red Hat</span></a></div></div><div style=3D"margi=
n-top:12px"><table border=3D"0" style=3D"color:rgb(0,0,0);font-family:RedHa=
tText,sans-serif;font-size:medium"><tbody><tr><td width=3D"100px"><a href=
=3D"https://www.redhat.com/" target=3D"_blank"><img src=3D"https://static.r=
edhat.com/libs/redhat/brand-assets/2/corp/logo--200.png" width=3D"90" heigh=
t=3D"auto"></a></td></tr></tbody></table><div><table border=3D"0" style=3D"=
color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small"=
><tbody><tr><td width=3D"100px"><i><br></i></td></tr></tbody></table><i><fo=
nt color=3D"#222222">&quot;If you are not willing to risk=C2=A0the usual, y=
ou will have to settle for the ordinary.&quot;</font></i></div></div></div>=
</div></div></div></div>

--0000000000003ef22705ce2a4a39--

--===============6978339917730445470==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG9jcyBtYWls
aW5nIGxpc3QgLS0gZG9jc0BsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1bnN1YnNjcmliZSBz
ZW5kIGFuIGVtYWlsIHRvIGRvY3MtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVkb3Jh
IENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVTL3By
b2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3JhcHJv
amVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBodHRw
czovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvZG9jc0BsaXN0cy5mZWRv
cmFwcm9qZWN0Lm9yZwpEbyBub3QgcmVwbHkgdG8gc3BhbSBvbiB0aGUgbGlzdCwgcmVwb3J0IGl0
OiBodHRwczovL3BhZ3VyZS5pby9mZWRvcmEtaW5mcmFzdHJ1Y3R1cmUK

--===============6978339917730445470==--