Silva 2.2 upgrade discussion
Andy Altepeter <[email protected]> Wed, 23 Sep 2009 20:41:41 -0500
| Newsgroups | gmane.comp.web.zope.silva.devel |
|---|---|
| Message-ID | <[email protected]> |
Greeting Devs! It's been a long time since the Silva 2.2 alpha was released. I wanted to get a discussion going about the Silva 2.2 upgrade. This is going to be a major upgrade. Silva 2.2 is switching to zope 3 technologies in many core areas. Some places are becoming fully zope 3, while others are adding support for grok, zope 3 views, forms, schema's, etc. One area of Silva 2.2 that is becoming fully zope 3 is the means by which metadata is stored. With 2.2, metadata will be stored as zope 3 annotations. This is good, but means the upgrade will be expensive as all metadata needs to be touched. If you're interested in testing Silva 2.2, at this point it will be best to do a fresh buildout from svn.infrae.com/buildout/silva/trunk . The Silva 2.2 alpha is too old now. You can read how to do this on docs.infrae.com, but it is pretty simple. We're soon going to need people to test the upgrade process. The 2.2 upgrade process isn't completely finished yet, in fact I'm still waiting on Sylvain to fix an odd upgrade condition, but for those not faint of heart please try it and give us some feedback! One important thing to note is that the 'services' tab in 2.2 is a grok view based on a marker interface, so it won't be visible until after the upgrade. It's easy to get to though; it's available at the same url, e.g.: http://zope.site.com:8080/silva/manage_services Please jump in to Silva 2.2 and test as much as you can. For this release especially, it will be very good to get as much "real world" testing as possible! peace, Andy Note for sylvain, the odd upgrade condition is this: The upgrade first refreshes the products. Three default products (Silva, SilvaDocument, SilvaLayout) all remove and recreate their metadata sets. Well, SilvaMetadata is now using z3 utility lookups. Unfortunately, the Silva Root isn't a z3 sitemanager yet! I'm unable to proceed with migrating namespaces until this is fixed :-)