Diff for "Translations/Specs/BazaarIntegration"

Not logged in - Log In / Register

Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2009-01-21 13:37:19
Size: 1381
Editor: danilo
Comment:
Revision 4 as of 2009-01-21 13:59:10
Size: 1688
Editor: danilo
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
https://blueprints.edge.launchpad.net/rosetta/+spec/import-templates-from-branch
Line 3: Line 4:
 * UI to select options for the sync: database patch, new LaunchpadForm most likely: (cost 3)
 * Writing branch job script to handle a branch by branch ID (cost 3)
 * [[https://blueprints.edge.launchpad.net/rosetta/+spec/import-templates-from-branch-ui-changes|UI to select options for the sync]]: database patch, new LaunchpadForm (cost 3)
 * [[https://blueprints.edge.launchpad.net/rosetta/+spec/import-templates-from-branch-scanner|Branch job script to handle a branch]] (cost 3)
Line 9: Line 10:
 * Auto-approve simple cases (no templates yet, one template only): (cost 3)  * [[https://blueprints.edge.launchpad.net/rosetta/+spec/import-templates-from-branch-auto-approval|Auto-approve simple cases]] (cost 3)
Line 14: Line 15:
 * Testing: pagetests for UI, unit tests for each of the steps  * Notes: testing — pagetests for UI, unit tests for each of the steps

Template import

https://blueprints.edge.launchpad.net/rosetta/+spec/import-templates-from-branch

Cost: 9

  • UI to select options for the sync: database patch, new LaunchpadForm (cost 3)

  • Branch job script to handle a branch (cost 3)

    • gets branch ID from branch scanner
    • find branch in Launchpad, check if it's the one that needs import (what productseries a branch is related to)
    • scanning the branch, finding POT files
    • putting those into import queue
  • Auto-approve simple cases (cost 3)

    • No templates yet in the database
    • Single template in the branch and in the database
    • Refactoring to be reusable
  • Notes: testing — pagetests for UI, unit tests for each of the steps

PO file import

Cost: 1

  • extend UI options
  • adapt the scanner to look for pofiles as well and put them into a queue

Commit PO files to a branch

Cost: 8

  • UI to select ProductSeries.translation_branch (db patch), branch picker for branches maintainer is allowed to push to (permissions) (cost 3)

  • Export everything and put to a branch: (cost 4)
    • Export it
    • Get a branch
    • Commit to it (overwriting files), careful with filenames and paths
    • Use same directory as the potemplate.path, normalize everything else
  • Allow loganberry/forster access to bazaar branch storage (to be able to commit) (cost 1)

Translations/Specs/BazaarIntegration (last edited 2009-03-24 08:53:30 by henninge)