(Created page with "This is a list of the docs packages we need created for each Fedora release, current as of February 2014 (list for Fedora 21). This list is based the document/language combi...") |
No edit summary |
||
| Line 74: | Line 74: | ||
Fedora-Virtualization_Getting_Started_Guide-VERSION-web-nl-NL | Fedora-Virtualization_Getting_Started_Guide-VERSION-web-nl-NL | ||
Fedora-Virtualization_Security_Guide-VERSION-web-en-US</pre> | Fedora-Virtualization_Security_Guide-VERSION-web-en-US</pre> | ||
'''Q: Why does Publican produce a separate docs package for each version of Fedora? Why not package the a piece of documentation for multiple versions of Fedora together, or at least every language for a particular document for a particualr version together?''' | |||
'''A:''' We package versions and languages separately to ease maintenance. For example, a build problem in one language (because of a flaw in somebody's PO file) should never block somebody else releasing the book in their language. Also, a half-finished and unproofread translation should never get published and put on public display just because another translator finished their work long ago and is itching to release. And of course, we don't want to block the English release because not all translations are ready yet. Similar considerations apply to docs for specific Fedora versions. If a translation team only completed the translation of a particular book for F17, and has half-finished, broken translations for F18, F16, and F15, we need to be able to publish the F17 version of the book without also publishing broken translations for three other Fedora releases, plus empty translations (ie, English text with Translated headings provided by our various tools) for everything else all the way back to FC1. | |||
[[category:Docs project]] | |||
Revision as of 02:15, 3 February 2014
This is a list of the docs packages we need created for each Fedora release, current as of February 2014 (list for Fedora 21).
This list is based the document/language combinations that have been published within the last three releases (ie, F18 → F20). We maintain this list to make life easier for Release Engineers; almost all the docs we will publish for a release are requested in a single ticket early in the release cycle. We should only have to go back and ask for more packages on a very infrequent basis.
As time goes by, of course, we hope that this standard list grows bigger, but we will also retire docs packages from this list if they have not been built for a particular language for more than three releases back.
In each case, replace VERSION by the version of Fedora for which we are publishing this document Fedora-Amateur_Radio_Guide-VERSION-web-en-US Fedora-Burning_ISO_images_to_disc-VERSION-web-bg-BG Fedora-Burning_ISO_images_to_disc-VERSION-web-web-cs-CZ Fedora-Burning_ISO_images_to_disc-VERSION-web-de-DE Fedora-Burning_ISO_images_to_disc-VERSION-web-en-US Fedora-Burning_ISO_images_to_disc-VERSION-web-es-ES Fedora-Burning_ISO_images_to_disc-VERSION-web-fi-FI Fedora-Burning_ISO_images_to_disc-VERSION-web-fr-FR Fedora-Burning_ISO_images_to_disc-VERSION-web-it-IT Fedora-Burning_ISO_images_to_disc-VERSION-web-ja-JP Fedora-Burning_ISO_images_to_disc-VERSION-web-nl-NL Fedora-Burning_ISO_images_to_disc-VERSION-web-pl-PL Fedora-Burning_ISO_images_to_disc-VERSION-web-pt-PT Fedora-Burning_ISO_images_to_disc-VERSION-web-ru-RU Fedora-Burning_ISO_images_to_disc-VERSION-web-sv-SE Fedora-Burning_ISO_images_to_disc-VERSION-web-uk-UA Fedora-Burning_ISO_images_to_disc-VERSION-web-zh-CN Fedora-Fedora_Live_Images-VERSION-web-cs-CZ Fedora-Fedora_Live_Images-VERSION-web-es-ES Fedora-Fedora_Live_Images-VERSION-web-ja-JP Fedora-Fedora_Live_Images-VERSION-web-ru-RU Fedora-FreeIPA_Guide-VERSION-web-en-US Fedora-Installation_Guide-VERSION-web-en-US Fedora-Installation_Guide-VERSION-web-ja-JP Fedora-Installation_Quick_Start_Guide-VERSION-web-cs-CZ Fedora-Installation_Quick_Start_Guide-VERSION-web-en-US Fedora-Installation_Quick_Start_Guide-VERSION-web-nl-NL Fedora-Musicians_Guide-VERSION-web-en-US Fedora-Musicians_Guide-VERSION-web-ja-JP Fedora-Power_Management_Guide-VERSION-web-en-US Fedora-Power_Management_Guide-VERSION-web-fr-FR Fedora-Power_Management_Guide-VERSION-web-ja-JP Fedora-Release_Notes-VERSION-web-bg-BG Fedora-Release_Notes-VERSION-web-en-US Fedora-Release_Notes-VERSION-web-es-ES Fedora-Release_Notes-VERSION-web-fr-FR Fedora-Release_Notes-VERSION-web-it-IT Fedora-Release_Notes-VERSION-web-ja-JP Fedora-Release_Notes-VERSION-web-lt-LT Fedora-Release_Notes-VERSION-web-nl-NL Fedora-Release_Notes-VERSION-web-ru-RU Fedora-Release_Notes-VERSION-web-sv-SE Fedora-Release_Notes-VERSION-web-uk-UA Fedora-Release_Notes-VERSION-web-zh-CN Fedora-Security_Guide-VERSION-web-en-US Fedora-Security_Guide-VERSION-web-es-ES Fedora-Security_Guide-VERSION-web-it-IT Fedora-Security_Guide-VERSION-web-ja-JP Fedora-System_Administrators_Guide-VERSION-web-en-US Fedora-Technical_Notes-VERSION-web-en-US Fedora-UEFI_Secure_Boot_Guide-VERSION-web-en-US Fedora-UEFI_Secure_Boot_Guide-VERSION-web-es-ES Fedora-UEFI_Secure_Boot_Guide-VERSION-web-fr-FR Fedora-UEFI_Secure_Boot_Guide-VERSION-web-ia Fedora-UEFI_Secure_Boot_Guide-VERSION-web-it-IT Fedora-UEFI_Secure_Boot_Guide-VERSION-web-nl-NL Fedora-UEFI_Secure_Boot_Guide-VERSION-web-pt-BR Fedora-UEFI_Secure_Boot_Guide-VERSION-web-ru-RU Fedora-UEFI_Secure_Boot_Guide-VERSION-web-uk-UA Fedora-Virtualization_Administration_Guide-VERSION-web-en-US Fedora-Virtualization_Getting_Started_Guide-VERSION-web-en-US Fedora-Virtualization_Getting_Started_Guide-VERSION-web-es-ES Fedora-Virtualization_Getting_Started_Guide-VERSION-web-ja-JP Fedora-Virtualization_Getting_Started_Guide-VERSION-web-nl-NL Fedora-Virtualization_Security_Guide-VERSION-web-en-US
Q: Why does Publican produce a separate docs package for each version of Fedora? Why not package the a piece of documentation for multiple versions of Fedora together, or at least every language for a particular document for a particualr version together?
A: We package versions and languages separately to ease maintenance. For example, a build problem in one language (because of a flaw in somebody's PO file) should never block somebody else releasing the book in their language. Also, a half-finished and unproofread translation should never get published and put on public display just because another translator finished their work long ago and is itching to release. And of course, we don't want to block the English release because not all translations are ready yet. Similar considerations apply to docs for specific Fedora versions. If a translation team only completed the translation of a particular book for F17, and has half-finished, broken translations for F18, F16, and F15, we need to be able to publish the F17 version of the book without also publishing broken translations for three other Fedora releases, plus empty translations (ie, English text with Translated headings provided by our various tools) for everything else all the way back to FC1.