> On Sat, 29 Jan 2000, Alexander Bokovoy wrote:
>
> > Yes, more likely will be 'replace' path for binaries at least :-).
> > Moreover, 1.2.6 will be
> > the next stable release of Midgard (probably the last before 2.0 but
> > who knows...)
>
> I don't think that that's what he means: in the past there has allways
> been a way to move the existing sites rather effortlessly to the
> new release. So the question probably is: will there be a way to
> upgrade that will not require recoding (parts of) the existing
> 1.2.5 sites.
>
> I think the move to 1.2.6 should be pretty safe. AFAICT there was
> a lot of functionality added but none changed, so the 1.2.x sites
> should still work as-is with 1.2.6.
>
> Alexander, is this correct?
Yes. Neither Admin Site nor Example Site occupy new IDs in database. I'm trying
to insert additional functionality into existed pages (it is hard but
possible). Though, the next release after 1.2.6 will probably add new IDs but
on that moment Midgard's database distribution system will not rely on real
database IDs and will modify adding data to fit into existing system.
--
Alexander Bokovoy
P.S. Ugh, hard work, but copying/deleting trees of topics/pages/styles is
working now, at least Midgard-lib level (as fast C routines), but will be
available via PHP tonight.
---------------------------------------------
This message was sent via BSPU MailMan server.
http://www.bspu.unibel.by/MailMan/
--
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]
