-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 Mar 2007, at 22:28, Tres Seaver wrote:
- Do we have any writeup about what folks who have been working at or
near the tip of the trunk should expect after such a merge?
Nothing will break when the upgrade script has been run, and the need
to do so is mentioned in CHANGES.txt and INSTALL.txt. I don't recall
any separate documentation what to do differently when other big
changes were introduced (the actions refactoring come to mind),
please correct me if I'm wrong - the core CMF code has always been
held up as the sample to look at. Matter of fact this change has
enjoyed much higher visibility and collaboration from most people who
will be directly affected.
- We should tag the tip before the merge, to give those who need
stability a place to hide, too.
Sure, no problem.
jens
P.S.: I'm down to 1 failing test on a trunk checkout that contains
the merge.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFF7eUuRAx5nvEhZLIRAiPmAKCkGyWxTMF4YZUYFOF8wOZTVfzx2QCfVl9m
HOEGgx30LwB0KL6lkU+yNmg=
=2Yn1
-END PGP SIGNATURE-
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
