Silva Issue Tracker Archive: Issue1673

 This tracker has been migrated to Launchpad. Please post new messages at: https://bugs.launchpad.net/silva.
Title test content upgrade from Silva 1.5 to Silva 1.6
Priority bug Status chatting
Superseder (list) Nosy List daniel, faassen, flynt, kitblake, lbenno, thisfred, yserrano (list)
Assigned To thisfred Topics Silva-1.6 (list)

Created on 2007-01-25.18:31:57 by faassen, last changed 2007-02-14.09:50:50 by thisfred.

Messages
msg9139 (view) Author: thisfred Date: 2007-02-14.09:50:49
Changed versions, as we were confusing 1.6 and 2.0 (which were at some point the
same) but this should be looked at before 2.0.
msg9117 (view) Author: mpetit Date: 2007-02-09.00:02:16
and don't forget that we use non-ascii characters wherever it is allowed and
where nobody thought of;-)
msg9045 (view) Author: flynt Date: 2007-01-26.10:33:29
Some observations in regard to Silva contents upgrade:

ExtFile. As it is not part of the Silva core, ExtFile is often not included in
the tests. However, any site using more and a bit larger assets is tempted
quickly to use ExtFile as otherwise the ZODB is blown up easily. And if ExtFile
is in use, any contents upgrade tests not involving ExtFile with assets in the
file system is not sufficient for real production situations. So, if possible,
don't forget ExtFile in the whole picture of contents in Silva WCMS.
(Remark: Even during the officially ordered tests for compatibility of
ExtFile-1.5.2 it has been obviously forgotten to test the upgrade procedure:
upgrading from Silva 1.4 to 1.5 with use of the ExtFile-1.5.2 gives trouble
(POSKey Errors); you have to stick first to ExtFile-1.4.2 for the upgrade before
you switch. The tester at Infrae did not find this. Additionally there are
problems in Silva-1.5 with Zope Exports Imports, when assets are used in the
filesystem. Again you get POSKey Errors when importing with all the assets in
the repository. You have to import without repository and only after import copy
the respective assets into the repository. Very strange behaviour.)

SilvaExtensions and Codesources. Maybe especially important to observe and check
for problems with the change from Silva-1.5 to 1.6 (and Zope-2.10)? 

I give these hints, as here at ETH with a lot of old contents now, upgrades
become more and more targets of critics. There are voices which state that we
shouldn't do any upgrades at all any more (which then would mean we would have
to freeze Silva with all consequences), because those people, especially from
mass hosting operation and helpdesk, are more and more scared of the Silva WCMS
upgrades and the bugs and work they imply.
msg9041 (view) Author: faassen Date: 2007-01-25.18:31:57
Test a content upgrade from Silva 1.5 to Silva 1.6. We don't expect content
changes but we need to verify it.
History
Date User Action Args
2007-02-14 09:50:50thisfredsettopic: - zope2.10
assignedto: thisfred
messages: + msg9139
title: test content upgrade from Silva 1.5 to Silva 2.0 -> test content upgrade from Silva 1.5 to Silva 1.6
2007-02-09 00:02:17mpetitsetmessages: + msg9117
2007-02-08 17:08:24danielsettitle: test content upgrade from Silva 1.5 to Silva 1.6 -> test content upgrade from Silva 1.5 to Silva 2.0
2007-01-26 10:33:30flyntsetstatus: unread -> chatting
nosy: + lbenno, yserrano
messages: + msg9045
2007-01-26 10:11:33flyntsetnosy: + kitblake
2007-01-26 10:10:33flyntsetnosy: + flynt
2007-01-25 18:31:57faassencreate