> Fom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
> I've patched PHP 3.0.14 yesterday and it will be default
> engine for Midgard
> 1.2.6 (if PHP team wouldn't force new release). I'll upload
> it (and other beta-
> stage changes for 1.2.6) to CVS repositary and to the Midgard
> 1.2.6 test corner
> site (http://www.midgard.f2s.com/) as soon as I can after
> fixing some code in
> Midgard modules. But Midgard 1.2.6 requires also small
> changes in the existing
> database structure (new table added to automate repositary
> checking), it will
> be documented in the tar-balls.
>
When do you expect Midgard 1.2.6 to be available in a usable form?
> Also Midgard 1.2.6 will introduce tools for distribution and
> updating database
> information between develope and production servers. It means
> that for updating
> Admin Site from 1.2.5 to 1.2.6 you'll not need to drop all
> your other data in
> database. Instead, you'll run some utility (code name
> 'Repligard') which tests
> your database and update only changed records. As soon as
> this utility will
> work stable, Midgard 1.2.6 will be officially released.
>
That sounds great. I'll be looking forward to it!
Thank you for your very informative reply.
Best regards
Jesper Juhl
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
