Hi,
For some time now, we've been upgrading a pretty medium-sized MMBase application every now and then. With every new release we've been adding builders, new allowed relations, etc. the way we think works, by just copying files & doing hard manual labour in the MMBase Admin area :)
Since we've been introduced to MMBase some time ago and sticked to a certain way of thinking as of then, we have a feeling our MMBase releasemanagement may not be the most effective way anymore. Sometimes it's even too time-consuming, so we were hoping if some of you MMBase professionals are willing to give some insight into your MMBase releaseprocedures?
I would even be glad if someone was able to give some pointers as to the order and how some of the typical MMBase operations occur during an upgrade.
-- Ted Vinke Software Developer First8 BV / Ewycksgroep
Groenestraat 294 | Postbus 31006 6531 JC Nijmegen | 6503 CA Nijmegen
t +31 (0)24 348 35 70 f +31 (0)24 348 35 71
[EMAIL PROTECTED] http://www.first8.nl _______________________________________________ Developers mailing list Developers@lists.mmbase.org http://lists.mmbase.org/mailman/listinfo/developers
