Add Miscellenous index and moved sop_eol, sop_fedora_media_writer
Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
This commit is contained in:
Samyak Jain
parent
96d9c091f1
commit
b1384ac17d
5 changed files with 28 additions and 141 deletions
|
|
@ -1,5 +1,7 @@
|
|||
* xref:index.adoc[Releng Miscellaneous guide]
|
||||
** xref:sop_generating_openh264_composes.adoc[Generate openh264 composes]
|
||||
** xref:sop_eol_change.adoc[Adjust EOLs and SLs on branches]
|
||||
** xref:sop_fedora_media_writer.adoc[Fedora Media Writer Building and Signing]
|
||||
** xref:sop_find_module_info.adoc[Find Module Information]
|
||||
** xref:sop_unretire.adoc[Unretire package branch]
|
||||
** xref:sop_update_critpath.adoc[Update Critpath]
|
||||
|
|
@ -13,4 +15,5 @@
|
|||
** xref:sop_clean_amis.adoc[Clean AMIs Process]
|
||||
** xref:sop_pushing_updates.adoc[Pushing Updates]
|
||||
** xref:sop_package_blocking.adoc[Package Blocking]
|
||||
* xref:sop.adoc[Fedora Release Engineering Standard Operating Procedures]
|
||||
* xref:troubleshooting.adoc[Fedora Release Engineering Troubleshooting Guide]
|
||||
|
|
@ -1,150 +1,34 @@
|
|||
== Fedora Release Engineering
|
||||
== Fedora Release Engineering Miscellaneous Guide
|
||||
|
||||
Contents:
|
||||
== Introduction ==
|
||||
|
||||
overview philosophy contributing troubleshooting architecture sop
|
||||
The Fedora Release Engineering team is responsible for ensuring the timely and successful release of Fedora Linux distributions. While many of the team's tasks are well-defined and documented, there are also miscellaneous tasks that arise from time to time that may not fit neatly into established release processes.
|
||||
|
||||
This page contains information about the Fedora Release Engineering
|
||||
team.
|
||||
This guide serves as a reference for those miscellaneous tasks. While these tasks may vary in nature and frequency, they are all important for the smooth functioning of the Fedora release process. By documenting these tasks and their associated procedures, this guide aims to provide transparency into the workings of the Fedora Release Engineering team and facilitate knowledge-sharing among team members.
|
||||
|
||||
[[releng-contact-info]]
|
||||
=== Contact Information
|
||||
Whether you're a member of the Fedora Release Engineering team, a contributor to Fedora, or simply interested in the release process, we hope you find this guide informative and useful.
|
||||
|
||||
* IRC: `#fedora-releng` on irc.libera.chat
|
||||
* Mailing List: https://admin.fedoraproject.org/mailman/listinfo/rel-eng[rel-eng@lists.fedoraproject.org]
|
||||
* Issue tracker: https://pagure.io/releng/new_issue[Fedora Releng Pagure Tickets]
|
||||
== List of Miscellaneous Tasks ==
|
||||
|
||||
If you want the to get something done (e.g. moving packages to
|
||||
buildroots or into frozen compositions) by the ReleaseEngineering Team,
|
||||
please create a ticket in the issue tracker mentioned above. Please
|
||||
enter your FAS-username or e-mail address in the respective textbox, to
|
||||
make sure the team can contact you.
|
||||
Here are some of the miscellaneous tasks performed by the Fedora Release Engineering team:
|
||||
|
||||
[[index-team-composition]]
|
||||
=== Team Composition
|
||||
* https://fedoraproject.org/wiki/User:kevin[Kevin Fenzi (nirik)]
|
||||
* https://fedoraproject.org/wiki/User:sharkcz[Dan Horák (sharkcz)](secondary arches)
|
||||
* https://fedoraproject.org/wiki/User:pbrobinson[Peter Robinson(pbrobinson)]
|
||||
* https://fedoraproject.org/wiki/User:maxamillion[Adam Miller(maxamillion)]
|
||||
* https://fedoraproject.org/wiki/User:humaton[Tomas Hrcka(humaton)]
|
||||
* link:sop_generating_openh264_composes[Generate openh264 composes]
|
||||
* link:sop_eol_change[Adjust EOLs and SLs on branches]
|
||||
* link:sop_fedora_media_writer[Fedora Media Writer Building and Signing]
|
||||
* link:sop_find_module_info[Find Module Information]
|
||||
* link:sop_unretire[Unretire package branch]
|
||||
* link:sop_update_critpath[Update Critpath]
|
||||
* link:sop_update_releng_docs[Update RelEng Rendered Docs]
|
||||
* link:sop_remote_dist_git_branches[Remove dist-git branches]
|
||||
* link:sop_package_unblocking[Package Unblocking]
|
||||
* link:sop_retire_orphaned_packages[Retire Orphaned Packages]
|
||||
* link:sop_requesting_task_automation_users[Requesting Automation Users]
|
||||
* link:sop_process_dist_git_requests[Process fedora-scm-requests tickets]
|
||||
* link:sop_signing_builds[Sign the packages]
|
||||
* link:sop_clean_amis[Clean AMIs Process]
|
||||
* link:sop_pushing_updates[Pushing Updates]
|
||||
* link:sop_package_blocking[Package Blocking]
|
||||
|
||||
Release Team members are approved by FESCo. However, FESCo has delegated
|
||||
this power to the Release Team itself. If you want to join the team,
|
||||
please read `join-releng`.
|
||||
== Conclusion ==
|
||||
|
||||
=== What is Fedora Release Engineering?
|
||||
|
||||
For a Broad Overview, see `overview <overview>`.
|
||||
|
||||
=== Why we do things the way we do them
|
||||
|
||||
For information on the Fedora Release Engineering Philosophy, see
|
||||
`philosophy <philosophy>`.
|
||||
|
||||
=== Fedora Release Engineering Leadership
|
||||
|
||||
Mohan Boddu (mboddu on IRC, FAS username mohanboddu)
|
||||
|
||||
Leadership is currently appointed by FESCo with input from the current
|
||||
release team.
|
||||
|
||||
=== Things we Do
|
||||
|
||||
* {blank}
|
||||
+
|
||||
Create official Fedora releases.::
|
||||
** {blank}
|
||||
+
|
||||
Fedora Products;;
|
||||
*** Cloud
|
||||
*** Server
|
||||
*** Workstation
|
||||
** Fedora Spins
|
||||
* Report progress towards release from
|
||||
https://fedoraproject.org/wiki/Releases/Branched[branched] creation on.
|
||||
* Give reports to FESCo on changes to processes.
|
||||
* If something is known to be controversial, we let FESCo know before
|
||||
implementing otherwise implementation generally happens concurrently to
|
||||
reporting.
|
||||
* Set policy on freeze management
|
||||
* Administrate the build system(s)
|
||||
* Remove unmaintained packages from Fedora
|
||||
* Push updated packages
|
||||
* write and maintain tools to compose and push Fedora
|
||||
|
||||
[[join-releng]]
|
||||
=== Joining Release Engineering
|
||||
|
||||
Much of rel-eng's communication is via IRC. One of the best ways to
|
||||
initially get involved is to attend one of the meetings and say that
|
||||
you're interested in doing some work during the open floor at the end of
|
||||
the meeting. If you can't make the meeting times, you can also ping one
|
||||
of us on IRC or sign up for the
|
||||
https://admin.fedoraproject.org/mailman/listinfo/rel-eng[mailing list].
|
||||
|
||||
Since release engineering needs special access to systems essential to
|
||||
Fedora people new to rel-eng will usually get access a little bit at a
|
||||
time. Typically people won't immediately be granted the ability to sign
|
||||
packages and push updates for example. A couple of tasks you could start
|
||||
out with are troubleshooting why builds are failing (and if rel-eng
|
||||
could take actions to fix it) as the requests are submitted to pagure or
|
||||
help with scripts for various rel-eng tasks.
|
||||
|
||||
There are also a number of tools that Fedora Release Engineering uses
|
||||
and relies upon, working on improving these upstream to fascilitate with
|
||||
new things that the Fedora Project is aiming to deliver is also a great
|
||||
way to get involved with Fedora Rel-Eng.
|
||||
|
||||
=== How we do it
|
||||
|
||||
See our `Standard Operating Procedures <sop>` for details on how we do
|
||||
the things we do.
|
||||
|
||||
Most discussions regarding release engineering will happen either in
|
||||
[.title-ref]##fedora-releng# or on the releng mailing list. For
|
||||
requests, please consult the `releng-contact-info`
|
||||
|
||||
=== Meetings
|
||||
|
||||
rel-eng holds regular meetings every Monday at 14:30 UTC in
|
||||
[.title-ref]##fedora-meeting-3# on the Libera IRC network.
|
||||
|
||||
* https://pagure.io/releng/issues?status=Open&tags=meeting[Meeting
|
||||
agendas] are created from open tickets in pagure that contain the
|
||||
meeting keyword.
|
||||
|
||||
==== Meeting Minutes
|
||||
|
||||
Minutes are posted to the rel-eng mailing list. They are also available
|
||||
at the
|
||||
https://meetbot.fedoraproject.org/sresults/?group_id=releng&type=team[Meetbot
|
||||
team page for releng]
|
||||
|
||||
There are also
|
||||
https://fedoraproject.org/wiki/ReleaseEngineering/Meetings[historical
|
||||
Meeting Minutes for 2007-04-16 to 2009-05-04].
|
||||
|
||||
=== Current activities
|
||||
|
||||
See our https://pagure.io/releng/issues[ticket queue] for the things we
|
||||
are currently working.
|
||||
|
||||
See https://fedoraproject.org/wiki/Releases[Releases] for information
|
||||
about Fedora releases, including schedules.
|
||||
|
||||
=== Freeze Policies
|
||||
|
||||
* https://fedoraproject.org/wiki/Milestone_freezes[Milestone (Alpha,
|
||||
Beta, Final) freezes]
|
||||
* https://fedoraproject.org/wiki/Software_String_Freeze_Policy[String
|
||||
Freeze Policy] (Same time as Alpha Freeze)
|
||||
* https://fedoraproject.org/wiki/Changes/Policy[Change freeze policy]
|
||||
(that's 'Change' as in 'feature')
|
||||
* https://fedoraproject.org/wiki/Updates_Policy[Updates Policy] (not
|
||||
technically a freeze, but of interest)
|
||||
|
||||
=== Indices and tables
|
||||
|
||||
* `genindex`
|
||||
* `modindex`
|
||||
* `search`
|
||||
This concludes the Fedora Release Engineering Miscellaneous Guide.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue