From Fedora Project Wiki

  • Changes/MySQL 8
    ...ease notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Targeted release: [[Releases/29 | Fedora 29 ]]
    7 KB (1,033 words) - 15:59, 19 February 2020
  • Changes/VA-API 1.0.0
    * Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/113 #113] * Targeted release: [[Releases/28 | Fedora 28 ]]
    6 KB (844 words) - 15:08, 2 March 2018
  • Changes/KDEWaylandByDefault
    ...ease notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Targeted release: [[Releases/28 | Fedora 28 ]]
    8 KB (1,227 words) - 16:31, 15 January 2018
  • Changes/StratisStorage
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...otes/issue/74 #74]<!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
    13 KB (2,068 words) - 14:36, 2 March 2018
  • Changes/389-ds-base-remove-686
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...ease notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
    11 KB (1,773 words) - 07:45, 9 April 2018
  • Changes/TZDATA-VANGUARD
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release. -->
    11 KB (1,781 words) - 08:48, 4 June 2018
  • Changes/GHC 8.2
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/108 #108]
    11 KB (1,817 words) - 11:45, 1 May 2018
  • Changes/Atomic Cloud and Docker images for s390x
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release. -->
    13 KB (2,040 words) - 05:19, 23 March 2018
  • Changes/ModularRelease
    = Modular Release = The build, release, distribution, and update changes associated with and required for the [[Ch
    17 KB (2,788 words) - 19:16, 3 November 2017
  • Changes/GifLib5
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/82 #82]
    10 KB (1,548 words) - 14:45, 2 March 2018
  • Changes/AnacondaModularization
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/105 #105]
    12 KB (1,982 words) - 15:03, 2 March 2018
  • Changes/Removing ldconfig scriptlets
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release. -->
    13 KB (2,166 words) - 15:07, 2 March 2018
  • Changes/CJKDefaultFontsToNoto
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...ease notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
    17 KB (2,683 words) - 18:33, 12 July 2018
  • Changes/RemoveObsoleteScriptlets
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release.
    15 KB (2,281 words) - 20:07, 3 January 2019
  • Changes/Fish 3.0
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release.
    21 KB (3,278 words) - 21:47, 12 February 2019
  • Changes/Ruby 2.5
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release. -->
    16 KB (2,477 words) - 08:22, 9 April 2018
  • Fedora 28 talking points
    ...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/28/ChangeSet|Change Set]] for this release.
    22 KB (3,054 words) - 15:03, 1 May 2018
  • Changes/Nodejs10
    ...t require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) .... This information is used for the overall changeset summary page for each release.
    28 KB (4,436 words) - 07:39, 18 June 2018
  • Common F28 bugs
    ..._bugs_header_stable_release}}</nowiki>. This should replace the entire pre-release header text. Please do this rather than copy/pasting. If you are making imp == Release Notes ==
    28 KB (4,423 words) - 21:28, 4 October 2018
  • Common F29 bugs
    ...release}}</nowiki>. Please do this rather than copy/pasting. At the time a release goes stable, replace this entire header with a '''SUBSTITUTION''' of [[Temp == Release Notes ==
    20 KB (3,205 words) - 01:31, 25 September 2019
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://fedoraproject.org/wiki/Special:Search"