Translate Toolkit & Pootle

Tools to help you make your software local

User Tools


How to release

This is a page that will try to serve as a checklist of things to do for an official release, see snapshots for creating developer releases.

Before

Wiki

  • Update wiki documentation
    • Branches, versions, etc.
    • Search and remove any vN.N comments that refer to old releases or the new release.
    • Ensure that all new command line items are added
    • New commands/formats/methods must be documented

API

  • Generate off-sourceforge and upload
  • Run ./bin/create-sitemaps

How to run the tools

  • You need to be the user 'builder'
    • The easiest way to do this is by running 'sudo -u builder bash'
  • Run bin/snapshot-toolkit to build the toolkit
    • If you want to build from a branch, pass the name of the branch (and not the full Subversion URL) as a command line parameter.
  • TBD

Afterwards

  • add new translations
  • deprecated since 0.10.1: Add/remove languages translations in pootlesetup.py
  • Enable / disable enabled languages in pootle.prefs
  • Any new scripts / packages to be specified in setup files?
  • test
  • update ChangeLog (do an svn up first in the directory where svn2cl is run from, otherwise you don't get the latest entries)
  • build
  • Documentation: epydoc?
  • sanity checks
  • Add the version in http://bugs.locamotion.org/
  • Sourceforge
    • Upload (see this page for instructions)
    • Do sourceforge release
    • Change default files suggested to users (keep in mind that Pootle and toolkit releases might not be synced, and recommending different versions could pose problems)
  • Remove built files from translate.sourceforge.net to save space
  • Announce in #pootle
  • tag
  • NEWS
  • Upstream releases
  • Report release to downstream packagers to upgrade (Fedora - Bugzilla e.g. #315021)
  • install :-)

Communication

Information Sites

Sites that carry information about the tools and that need updating.