Search results

* 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)