Members-Desktopguide
|
Size: 2222
Comment:
|
Size: 2785
Comment: seeking sponsorship
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| This page offers guidance for documentation committers working with the desktop guide project. It is a supplement to [[https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/Repository/Members|the main Members page]]. | This page offers guidance for documentation committers working with the desktop guide project. It is a supplement to [[DocumentationTeam/SystemDocumentation/Repository/Members|the main Members page]]. |
| Line 7: | Line 7: |
| This page is not intended for desktop guide contributors, who should be using the [[https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide|desktop guide contributors focus page]] instead. | This page is not intended for desktop guide contributors, who should be using the [[DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide|desktop guide contributors focus page]] instead. |
| Line 9: | Line 9: |
| == Checklist for releasing the ubuntu-docs package == | == Preparations for new cycle == Soon after FinalRelease of an Ubuntu version, it's time to make some preparations for the next cycle. * Set up translations for the new development version project, and enable synchronization with the translations for the corresponding package version. * New version number in these files: * configure.in * html/Makefile * html/ubuntu.xsl == Releasing the ubuntu-docs package == |
| Line 13: | Line 23: |
| There are some key steps that should be taken before [[DocumentationStringFreeze]]. | There are some key steps that should be taken before DocumentationStringFreeze. |
| Line 16: | Line 26: |
* Version number in * configure.in * html/Makefile * html/ubuntu.xsl |
|
| Line 33: | Line 38: |
| * Build a source package from lp:ubuntu-docs and upload to the main archive. (Requires upload rights for ubuntu-docs.) | * Build a source package from lp:ubuntu-docs and upload to the main archive.<<BR>>If you don't have upload rights for ubuntu-docs, this step has to be carried out by a sponsor, i.e. a [[https://launchpad.net/~ubuntu-core-dev|core developer]]. Due to the coordination with the translators, ubuntu-docs uploads are time critical, so adding a bug to the [[http://reqorts.qa.ubuntu.com/reports/sponsoring/|sponsorship queue]] does not apply. Instead pinging someone on IRC is the way to go. |
| Line 35: | Line 40: |
| The build process will update the PO files in Rosetta with the updated ubuntu-help.pot. lp:ubuntu/ubuntu-docs will be updated automatically. | The new ubuntu-help.pot will be reflected in PO files that are exported from Rosetta.<<BR>> lp:ubuntu/ubuntu-docs is updated automatically. |
| Line 37: | Line 43: |
| === After LanguagePackTranslationDeadline === | === After NonLanguagePackTranslationDeadline === |
| Line 39: | Line 45: |
| [[LanguagePackTranslationDeadline]] coincides with [[FinalFreeze]], so at this point we are in a hurry. | NonLanguagePackTranslationDeadline happens one week before FinalFreeze, so at this point we are in a hurry. |
| Line 41: | Line 47: |
| * Import the PO files from Rosetta to lp:ubuntu-docs | * Export the PO files from Rosetta and commit them to lp:ubuntu-docs.<<BR>>Notes: 1. Download __the project's__ tarball, e.g. from https://translations.launchpad.net/ubuntu-docs/trusty/+export for trusty. 2. Use the update-translations.sh script to extract the files. |
| Line 43: | Line 51: |
| * Update the changelog | * Update the changelog. |
| Line 45: | Line 53: |
| * Since we are close to [[FinalRelease]], we may need a confirmation from the [[ReleaseTeam]] (if we don't already have it implicitly due to the nature of the ubuntu-docs package). * Build a source package from lp:ubuntu-docs and upload to the main archive. (Requires upload rights for ubuntu-docs.) |
* Upload to the archive. |
Contents
|
This page offers guidance for documentation committers working with the desktop guide project. It is a supplement to the main Members page.
This page is not intended for desktop guide contributors, who should be using the desktop guide contributors focus page instead.
Preparations for new cycle
Soon after FinalRelease of an Ubuntu version, it's time to make some preparations for the next cycle.
- Set up translations for the new development version project, and enable synchronization with the translations for the corresponding package version.
- New version number in these files:
- configure.in
- html/Makefile
- html/ubuntu.xsl
Releasing the ubuntu-docs package
Before DocumentationStringFreeze
There are some key steps that should be taken before DocumentationStringFreeze.
Update certain files
- ubuntu-help/C/whats-new.page
- debian/changelog
- ubuntu-help/ubuntu-help.pot
- Run autogen.sh.
- (Re)move the old ubuntu-help.pot.
- Run the command 'make ubuntu-help.pot' from the ubuntu-help folder.
Upload to the archive
Build a source package from lp:ubuntu-docs and upload to the main archive.
If you don't have upload rights for ubuntu-docs, this step has to be carried out by a sponsor, i.e. a core developer. Due to the coordination with the translators, ubuntu-docs uploads are time critical, so adding a bug to the sponsorship queue does not apply. Instead pinging someone on IRC is the way to go.
The new ubuntu-help.pot will be reflected in PO files that are exported from Rosetta.
lp:ubuntu/ubuntu-docs is updated automatically.
After NonLanguagePackTranslationDeadline
NonLanguagePackTranslationDeadline happens one week before FinalFreeze, so at this point we are in a hurry.
Export the PO files from Rosetta and commit them to lp:ubuntu-docs.
Notes:Download the project's tarball, e.g. from https://translations.launchpad.net/ubuntu-docs/trusty/+export for trusty.
- Use the update-translations.sh script to extract the files.
- Update the changelog.
- Upload to the archive.
Generate the HTML pages and upload to help.ubuntu.com (see BuildingDocumentation).
DocumentationTeam/SystemDocumentation/Repository/Members-Desktopguide (last edited 2015-09-09 00:06:31 by dsmythies)