From Fedora Project Wiki
(Write out the compat guarantees section) |
(Add release notes section to the template.) |
||
| Line 44: | Line 44: | ||
<!-- Fill in this section with any guarantees you wish to make for packages in the SCL. See https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_%28draft%29#Compatibility_Guarantees for examples of what makes a good guarantee. --> | <!-- Fill in this section with any guarantees you wish to make for packages in the SCL. See https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_%28draft%29#Compatibility_Guarantees for examples of what makes a good guarantee. --> | ||
== Release Notes and Change History == | |||
<!-- Change N to the Fedora release that this SCL is first appearing in --> | |||
=== Fedora N === | |||
<!-- Fill in this section with information that should go in the release notes for this new SCL --> | |||
<!-- If the Compat Guarantees change or you must change something in the Compat Guarantees in an incompatible manner be sure to update this section with additional entries: | |||
=== Fedora N2 === | |||
* Had to change the behaviour of url.get() when retrieving https sites due to security risk. This function now fails if the server's certificates are invalid or cannot be verified. An optional parameter, allow_broken, can restore the former behaviour if you are willing to assume the security risk. | |||
* The db library code was updated because upstream no longer supports the old library and the old code had too many security flaws. The new version has an incompatible file format. We ship a script /usr/bin/convert_db that can convert from the old format to the new one but it must be run on each db file before the library can read it. It's beyond the scope of this SCL to determine what an application chooses to do if it encounters a db file it doesn't know what to do with so there's the chance that an application may choose to overwrite old db files instead of letting you upgrade them. Please take backups. | |||
--> | |||
[[Category:SCL Definiton (draft)]] | [[Category:SCL Definiton (draft)]] | ||
Latest revision as of 18:21, 22 May 2014
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR SCL REQUEST.
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR SCL REQUEST.
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. This is a draft SCL Definition. It needs to be approved by the FPC before an SCL following this draft can be created. The FPC uses the criteria on https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_(draft)#SCL_Criteria to evaluate whether the SCL is okay for Fedora.
It is still under construction and content may change. Do not rely on the information on this page. This is a draft SCL Definition. It needs to be approved by the FPC before an SCL following this draft can be created. The FPC uses the criteria on https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_(draft)#SCL_Criteria to evaluate whether the SCL is okay for Fedora.
SCL Name
Summary
Maintainers
- Names:
- Maintainer Name - <email address>
- Maintainer2 Name - <maintainer2 email address>
Detailed Description
Packages in the Platform
The following packages are part of the platform that this SCL implements. Packages which are built for the SCL but not mentioned here are not part of the platform and may be removed or changed in incompatible ways according to normal Fedora Policies (Usually, when a new release of Fedora is made).
- <package name>
- <package2 name>
Compatibility Guarantees
The packages in an SCL's platform are often more concerned with maintaining backwards compatibility than other packages in Fedora as SCLs exist to provide you with a more stable platform to build your own cross-platform software. As such, many of the packages in the SCL have specific compatibility guarantees. This section defines which packages in this SCL have more strict backwards compatibility guarantees and what those guarantees are so that you know what to expect.
Security trumps compatibility
If a security issue needs to be fixed but that breaks backwards compatibility, the security issue will be fixed despite violating the guarantee. This page will be updated to mention the Fedora versions and the version of the relevant packages from the SCL which needed a backwards incompatible change to fix the issue).
If a security issue needs to be fixed but that breaks backwards compatibility, the security issue will be fixed despite violating the guarantee. This page will be updated to mention the Fedora versions and the version of the relevant packages from the SCL which needed a backwards incompatible change to fix the issue).
Guarantees are only best effort
SCL maintainers attempt to keep these backwards compatibility guarantees but the guarantees are not set in stone. As an example, the guarantees could be changed if the maintainer of an SCL decides to orphan it and someone new takes over. The new maintainer may decide to guarantee backwards compatibility for a smaller set of packages or make incompatible updates to some of the existing packages. These types of changes can only occur between Fedora releases.
SCL maintainers attempt to keep these backwards compatibility guarantees but the guarantees are not set in stone. As an example, the guarantees could be changed if the maintainer of an SCL decides to orphan it and someone new takes over. The new maintainer may decide to guarantee backwards compatibility for a smaller set of packages or make incompatible updates to some of the existing packages. These types of changes can only occur between Fedora releases.