Search results

{{header|docs}} ...erested in a topic in direct contact with the developers of the software. Developers get to know who is their writer, and can send over information knowing it w

export CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/docs export CVSROOT=:ext:mdious@cvs.fedoraproject.org:/cvs/docs

{{header|docs}} # Edit the content directly within the appropriate beat at [[Docs/Beats| Docs/Beats]]. '''This is the best option ''by far'', since all account holders

This document tracks the process of taking [[Docs/Beats| Docs/Beats]] and converting it to the release notes. At some point it hands of ...ted in a nagmail that is sent to one or more public locations to encourage developers to get their content changes in or be removed from the notes

{{header|docs}} ...Node.js applications should notice no problems from this change, although developers should review the upstream release notes and API changes:

{{header|docs}} Assist developers and package maintainers with the creation and maintenance of feature pages

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ...argeting developers, among others. Software collections are aiming to give developers easy access to the tools they need.

* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/550 #550] ...ed in the [https://docs.fedoraproject.org/en-US/iot/edition-promotion/ IoT docs]. This change is primarily a paperwork exercise as the necessary work has b

...leaseNotes/Process| the Process page]] for details and start editing at [[Docs/Beats| ]] today.}} ...21rc1 based kernel. Current release information is being tracked on the [[Docs/Beats/Kernel| kernel release notes source]] page.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> Many developers prefer to work with [https://www.vagrantup.com/ Vagrant] for their developm

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/213 #213]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * ARM developers can now use virt-manager/libvirt to manage ARM VMs without [[Architectures/

...ite you. Note, some Beats are committed to git://git.fedorahosted.org/docs/release-notes.git as they are written. Thank the developers, porters, project leaders, Fedora contributers, and Red Hat employees who m

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ** Use %packages --excludedocs to to skip installing docs.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/273 #273]

It is intended for Developers, Students and Hobbyists for common development purposes. anjuta-docs

...ing our OpenStack story has the potential to bring new users and OpenStack developers into the Fedora community. Horizon will play a vital part in improving our * [http://docs.openstack.org/ Upstream openstack docs]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/277 #277]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> Developers who use statically linked applications will have more information at hand w

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/274 #274]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/276 #276]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: Just voluntary rebuilds using the new system gcc, if things fail, look at

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers:

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/275 #275]

{{header|docs}} ...pted features for the upcoming release, and once past feature freeze, many developers will begin working on the next+1 release, and that work will appear in Rawh

<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: Be aware of possible provenpackager changes. Update other packages on best

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

...imarily used as a '''collaboration tool for our contributor community''' — developers, packagers, designers, writers, translators, quality assurance, and so on. ...der-right: 36PX solid white;"| [[Image:overview-docs-icon.png|link=https://docs.fedoraproject.org/]]

...leaseNotes/Process| the Process page]] for details and start editing at [[Docs/Beats| ]] today.}} ...21rc1 based kernel. Current release information is being tracked on the [[Docs/Beats/Kernel| kernel release notes source]] page.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other Developers: N/A (Not a System Wide Change)

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[ * Other developers:

'README-RETIRED.txt' in the %docs section which says this software * Other developers:

...fedorahosted.org/gcc-python-plugin/ embeds Python within GCC]. Interested developers should be able to use this to easily extend GCC by writing Python scripts, The plugins will allow interested developers to extend GCC in Python 2 and Python 3, without needing to deal with the C

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: Add a Workstation-specific service configuration (preset ?) to the firewal

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/281 #281]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> Developers: [https://plus.google.com/110830723758089847922 Axel Davy] (davyaxel@free.f

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team * Other developers:

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: Currently, around 400 packages FTBFS if this flag is enabled. A list of pa

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: System Wide Change <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/272 #272]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ...implementation for Anaconda developers. Developers of other extensions and developers of plugins that are not part of yum-utils will have to update their code.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: GNOME control-panel developers (if changes are necessary there)

...imarily used as a '''collaboration tool for our contributor community''' — developers, packagers, designers, writers, translators, quality assurance, and so on. ...der-right: 36PX solid white;"| [[Image:overview-docs-icon.png|link=https://docs.fedoraproject.org/]]

{{header|docs}} ...t the docs, you can learn how [https://docs.fedoraproject.org/en-US/fedora-docs/contributing/ here]. }}

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/266 #266]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> This feature aims to reduce the technical hurdles for users and developers to locate software packaged for a distribution, but which needs to be clear

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> it is to Fedora's advantage that developers will be able to install it easily.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Developers interested in trying AArch64 can now use virt-manager/libvirt to manage ARM

# eclipse-mylyn-docs '''DONE''' ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp

...dencies were strightened and packed into individual libraries. This allows developers and projects outside the KDE ecosystem to make use of these technologies an * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->

It's a tool for developers, hackers, system builders, engineers. Normal users should never see or both ...itly in the kernel via audit=0. Of course, as this is primarily a tool for developers/hackers/gurus adding the kernel command line option isn't too hard. Getting

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/386 #386]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: First few days/weeks just voluntary rebuilds using the new system gcc, if

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: [[User:Cicku|Christopher Meng]](package review/testing)<!-- REQUIRED FOR S

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/618 #618] infra-docs

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a la ...her packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, comp

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers:

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ...versions are intended to be installed need to be changed to install their docs into appropriately versioned subdirs, for example explicitly using the prev

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: Cloud WG

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: kaie (for ca-certificates)

...|| [[Extras| Extras]] ||[[Ambassadors| Ambassadors & Marketing ]] || [[docs| Documentation]] || [[kadischi| Kadischi]] || [[l18n| L10N]] {{Anchor|docs}}

For developers working with the ACPI subsystem, there are tools available from the referen * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/182 #182]

* Release notes owner: <To be assigned by docs team><!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/292 #292]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/183 #183]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/538 #538]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/130 #130]

* Release notes owner: <To be assigned by docs team> <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a la

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

The Kolab server will be available out of the box for users and developers. <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a la

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Developer requests update approval from Docs team * Docs team approves update text

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: First few days/weeks just voluntary rebuilds using the new system gcc, if

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a lar

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/402 #402]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: First few days/weeks just voluntary rebuilds using the new system gcc, if

<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a la [[KDE/Docs/DesktopUserGuide|Fedora KDE Desktop User Guide (draft)]]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: N/A (not a System Wide Change)

* Release notes owner:<!-- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Other developers: <code>redhat-rpm-config</code> needs to be updated accordingly. Some tool

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/574 #574]

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/299 #299]