Release Engineering

In order to get as much testing as possible, we announce pre-releases ( alpha1, beta1, beta1, RC1, RC2 and RC3 ) in the qa blog < https://qa.blog.documentfoundation.org/ >, Bugzilla, and the ReleaseNotes

Steps:
1. Create the release plan wiki page --> See https://redmine.documentfoundation.org/issues/2942#change-17290
2. Create the banner --> https://wiki.documentfoundation.org/QA/BugHuntingSession/Organization#LibreOffice_6.0_Testing_Series. E.g: https://wiki.documentfoundation.org/File:BHS_large_6.3_RC3.png
3. Update https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases with the correct links
4. Add [[File:BHS_large_6.3_RC3.png|600px|center|link=https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases]] to https://wiki.documentfoundation.org/ReleaseNotes/6.3 (Use versioning accordingly )
5. In Bugzilla, Go to "Administration - Parameters - General" and add

<center><a href="https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases&quot;>
<img border="0" src="https://wiki.documentfoundation.org/images/7/7f/BHS_large_6.3_RC3.png&quot; width="500" height="125"></a></center>

to announcehtml (Use versioning accordingly )
6. Write a blog post in the QA blog. E.g: https://qa.blog.documentfoundation.org/2019/07/09/libreoffice-6-3-rc1-ready-for-testing/ (Use versioning accordingly )

Before the final release, remove the banner from Bugzilla and the ReleaseNotes wiki page