⇤ ← Revision 1 as of 2010-04-20 09:06:38
1052
Comment:
|
1093
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
* Being enabled for `staging`. '''TODO: what db-devel revision?''' | * Being enabled for `staging`. '''TODO: what production-configs revision? How will we know it's landed?''' |
Trying out template generation on dogfood/staging
Right now we have no good test platform for this: staging has no build farm, and dogfood has no codehosting. Expect this page to change a lot as we work and learn.
Config
Make sure that generating templates is enabled in the Launchpad lazr config.
Enabled for dogfood.
- Enabled on development systems.
Being enabled for staging. TODO: what production-configs revision? How will we know it's landed?
Suitable branches
We don't yet know for sure what real-world branches will work right out of the box. We must fix that!
According to wgrant, editing configure.ac to set GETTEXT_PACKAGE ("or something like that") does the trick.
TODO: Easy litmus test to see if a branch will work with pottery.
TODO: Find good real-world sample branch for testing—preferably small but with multiple templates.
Once you have a suitable branch, you can copy it to staging's codehosting using "bzr push -d lp:<branch> lp://staging/<branch> --use-existing-dir"