Update the release-engineering overview page
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>
This commit is contained in:
Michal Konecny
parent
0a9b6ad6ba
commit
7d04774b73
1 changed files with 36 additions and 59 deletions
|
|
@ -1,18 +1,14 @@
|
|||
== Fedora Release Engineering
|
||||
|
||||
Contents:
|
||||
|
||||
overview philosophy contributing troubleshooting architecture sop
|
||||
= Fedora Release Engineering
|
||||
|
||||
This page contains information about the Fedora Release Engineering
|
||||
team.
|
||||
|
||||
[[releng-contact-info]]
|
||||
=== Contact Information
|
||||
[#releng-contact-info]
|
||||
== Contact Information
|
||||
|
||||
* matrix: `#releng:fedoraproject.org`
|
||||
* 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/new_issue[Fedora Releng Pagure Tickets]
|
||||
* 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,
|
||||
|
|
@ -20,46 +16,33 @@ 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.
|
||||
|
||||
[[index-team-composition]]
|
||||
=== 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)]
|
||||
* 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`.
|
||||
please read <<join-releng>>.
|
||||
|
||||
=== What is Fedora Release Engineering?
|
||||
== Fedora Release Engineering Leadership
|
||||
|
||||
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
|
||||
|
||||
(@jnsamyak:matrix.org on matrix, FAS username jnsamyak)
|
||||
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
|
||||
== Things we Do
|
||||
|
||||
* {blank}
|
||||
+
|
||||
Create official Fedora releases.::
|
||||
** {blank}
|
||||
+
|
||||
Fedora Products;;
|
||||
*** Cloud
|
||||
*** Server
|
||||
*** Workstation
|
||||
** Fedora Spins
|
||||
* 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.
|
||||
|
|
@ -72,10 +55,10 @@ reporting.
|
|||
* Push updated packages
|
||||
* write and maintain tools to compose and push Fedora
|
||||
|
||||
[[join-releng]]
|
||||
=== Joining Release Engineering
|
||||
[#join-releng]
|
||||
== Joining Release Engineering
|
||||
|
||||
Much of rel-eng's communication is via matrx. One of the best ways to
|
||||
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
|
||||
|
|
@ -95,36 +78,36 @@ 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
|
||||
== How we do it
|
||||
|
||||
See our `Standard Operating Procedures <sop>` for details on how we do
|
||||
the things we do.
|
||||
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
|
||||
[.title-ref]##fedora-releng# or on the releng mailing list. For
|
||||
requests, please consult the `releng-contact-info`
|
||||
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
|
||||
== Meetings
|
||||
|
||||
rel-eng holds regular meetings every Tuesday at 17:00 UTC in
|
||||
[.title-ref]##meeting-3:fedoraproject.org on matrix.
|
||||
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].
|
||||
|
||||
* https://pagure.io/releng/issues?status=Open&tags=meeting[Meeting
|
||||
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
|
||||
|
||||
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]
|
||||
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
|
||||
== Current activities
|
||||
|
||||
See our https://pagure.io/releng/issues[ticket queue] for the things we
|
||||
are currently working.
|
||||
|
|
@ -132,7 +115,7 @@ are currently working.
|
|||
See https://fedoraproject.org/wiki/Releases[Releases] for information
|
||||
about Fedora releases, including schedules.
|
||||
|
||||
=== Freeze Policies
|
||||
== Freeze Policies
|
||||
|
||||
* https://fedoraproject.org/wiki/Milestone_freezes[Milestone (Alpha,
|
||||
Beta, Final) freezes]
|
||||
|
|
@ -142,9 +125,3 @@ Freeze Policy] (Same time as Alpha Freeze)
|
|||
(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`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue