revno: 1595
fixes bug(s): https://launchpad.net/bugs/642898
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Mon 2010-09-20 09:29:32 +0200
message:
always create core schema for new databases (LP: #642898)
Hello Zeitgeist Framework Team,
On 2010-09-20 07:35z (just requested), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
Hello Zeitgeist Framework Team,
On 2010-09-20 07:35z (just requested), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.5 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
** Branch linked: lp:zeitgeist
--
Upgrading database scheme is broken for newly created databases
https://bugs.launchpad.net/bugs/642898
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
Public bug reported:
We have to discuss how to support versions jump in the upgrade path of
our db schema, like from (core, 0) to (core, 2). This becomes even
more important when we reach the next version.
For me there are two solution:
1.) write 'dummy' upgrade scripts, like core_0_2.py, which
I discussed this issue with Siegfried yesterday, and I would like to bring the
overall translation workflow to everybody's attention again:
* We want to make our ontology 'symbols' translatable
* logging output should not be translated
* we might need translation support for tools in tools/
*
+1 the transaltions happening in trunk are annoying as hell
On Mon, Sep 20, 2010 at 9:57 AM, Markus Korn thek...@gmx.de wrote:
I discussed this issue with Siegfried yesterday, and I would like to bring
the overall translation workflow to everybody's attention again:
* We want to make our
7 matches
Mail list logo
