Hi, I was updating one of the proposals in this minutes and had a somewhat hard time to define a goal. I stumbled over the upcoming problem of defining the Zope 3 core and came up with this footnote for myself:
Maybe this can be used as a spark to spur some discussion about the term 'Zope 3 core'. Maybe we need new terms in the future, maybe we need to re-define 'Zope 3 core'. Here is the version that appeared to me today: .. [1] Zope 3 core With the upcoming fuzzyness of the Zope 3 core, I found a somewhat interesting definition for me that defines the core as the set of packages that gets labeled with the same release tag together (there can be other ways of labeling that using a SVN tag of course) and that we apply the full rigid development practices for Zope 3 on. IMHO therefore being in 'the core' for a Zope 3 package guarantees a certain quality level. Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
