Hello, On Wed, 18 Jun 2008, Thomas Koch wrote:
> For my implementation of a proof of concept content repository[1] I need to > change the database schema on the fly. Changing schemas during production is > not that uncommon: The search function of eZPublish used to create temporary > tables and in ERP software you normally create temporary tables to analyze > data. As we had some issues with some feature creeping in in a sort of suboptimal way (memcache support for Cache), we're going to be a bit stricter on allowing new functionality into the eZ Components. This just means that we'll require a requirements[1] and design document[2] for every new non-trivial feature like we described in our development process[3]. I would therefore invite you to write a requirements document that we then can discuss. [1] http://svn.ez.no/svn/ezcomponents/docs/guidelines/requirements_doc.txt [2] http://svn.ez.no/svn/ezcomponents/docs/guidelines/design_doc.txt [3] http://ezcomponents.org/contributing/dev_process regards, Derick -- Derick Rethans eZ components Product Manager eZ systems | http://ez.no -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
