7d04774b73
There were plenty of outdated information on index page for release engineering. I fixed the syntax to work with asciidoc and updated information. There could still be some outdated info, but at least there will be less of it. Signed-off-by: Michal Konecny <mkonecny@redhat.com>
127 lines
4.9 KiB
Text
127 lines
4.9 KiB
Text
= Fedora Release Engineering
|
|
|
|
This page contains information about the Fedora Release Engineering
|
|
team.
|
|
|
|
[#releng-contact-info]
|
|
== Contact Information
|
|
|
|
* matrix: link:https://matrix.to/#/#releng:fedoraproject.org[Matrix Fedora releng channel]
|
|
* Mailing List: https://admin.fedoraproject.org/mailman/listinfo/rel-eng[rel-eng@lists.fedoraproject.org]
|
|
* Issue tracker: https://pagure.io/releng/issues[Fedora Releng Pagure Tickets]
|
|
|
|
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.
|
|
|
|
== 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)]
|
|
* https://fedoraproject.org/wiki/User:Jnsamyak[Samyak Jain (jnsamyak)]
|
|
|
|
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>>.
|
|
|
|
== Fedora Release Engineering Leadership
|
|
|
|
https://fedoraproject.org/wiki/User:Jnsamyak[Samyak Jain (jnsamyak)]
|
|
|
|
Leadership is currently appointed by FESCo with input from the current
|
|
release team.
|
|
|
|
== Things we Do
|
|
|
|
* Create official Fedora releases.
|
|
** 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 matrix. 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 matrix 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 xref:releng_misc_guide:index.adoc[Releng Miscellaneous guide]
|
|
and xref:release_guide:release_process.adoc[Release process] for details on how we
|
|
do the things we do.
|
|
|
|
Most discussions regarding release engineering will happen either in
|
|
link:https://matrix.to/#/#releng:fedoraproject.org[Matrix Fedora releng channel]
|
|
or on the releng mailing list.
|
|
For requests, please consult the <<releng-contact-info>>
|
|
|
|
== Meetings
|
|
|
|
Rel-eng holds regular meetings every Tuesday at 16:00 UTC in
|
|
link:https://matrix.to/#/#meeting-3:fedoraproject.org[Fedora Meeting 3 channel on matrix].
|
|
|
|
link: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
|
|
|
|
Meeting minutes are available at the
|
|
https://meetbot.fedoraproject.org/[Meetbot page].
|
|
|
|
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)
|