On Mon, 22 Dec 2008, F Wolff wrote:
> We'll definitely need to ship with migration scripts - at least from the
> jToolkit prefs to the format of the next release. I'm not aware of many
> people using the version on trunk before we migrated to Django (I also
> wouldn't have recommended it for pr
On Ma, 2008-12-22 at 01:04 -0800, Asheesh Laroia wrote:
> I presume that we plan to provide a graceful migration path forward for
> those still running Pootle 1.2.x (jToolkit Pootle, or "jTootle") into the
> new, Django Pootle ("Djootle") world.
>
> I already migrated our data from jTootle to Mo
On Monday 22 December 2008 10:36:02 Asheesh Laroia wrote:
> On Mon, 22 Dec 2008, Asheesh Laroia wrote:
> > IntegrityError: pootle_app_pootleprofile.ui_lang_id may not be NULL
> >
> > ui_lang = models.ForeignKey('Language', blank=True)
>
> zejn again to the rescue; he points out it shoul
On Mon, 22 Dec 2008, Asheesh Laroia wrote:
> IntegrityError: pootle_app_pootleprofile.ui_lang_id may not be NULL
> ui_lang = models.ForeignKey('Language', blank=True)
zejn again to the rescue; he points out it should be:
ui_lang = models.ForeignKey('Language', blank=True, nu
I presume that we plan to provide a graceful migration path forward for
those still running Pootle 1.2.x (jToolkit Pootle, or "jTootle") into the
new, Django Pootle ("Djootle") world.
I already migrated our data from jTootle to Mozootle, and I'm working on
an importer that migrates from jTootle
Congratulations on getting through the Mozootle milestone and onto this
major project! I'll be happy to help here and there as updating Pootle
corresponds to my duties at Creative Commons.
On Fri, 12 Dec 2008, Wynand Winterbach wrote:
> The most recent code in our repository already contains a
