Template import
Cost: 9
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)
- 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 (no templates yet, one template only): (cost 3)
- No templates yet in the database
- Single template in the branch and in the database
- Refactoring to be reusable
- 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)