-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Theune wrote: > Hi, > > Am Donnerstag, den 03.05.2007, 13:18 -0400 schrieb Tres Seaver: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Fred Drake wrote: >>> On 5/3/07, Christian Theune <[EMAIL PROTECTED]> wrote: >>>> I started moving packages to their own projects (manually right now, >>>> preparing for doing this scripted) and noticed that zope.index is >>>> tracked with a specific revision number. >>>> >>>> My understanding is that the trunk of the Zope 3 tree should be tracking >>>> the trunk of the satellite project's tree without pinning it to a >>>> revision. >>> Probably my fault; I've become really wary of externals that aren't >>> specific. >>> >>> Frankly, I don't *really* care how the Zope 3 tree refers to satellite >>> projects. My hope is that I can very quickly get away from ever >>> looking at the Zope 3 conglomeration (checkout or release), and only >>> use the satellite projects. >>> >>> Conversely, I care very much about the satellite projects not >>> referring to the Zope 3 tree, and look forward to what you're working >>> on today. >> When a truly egg-based Zope3 ships, it should be a meta-egg with >> explicitly-versioned dependencies. >> >> Approximating that in tree would be to have the Zope3 tree point at >> *tagged releases* of the satellite projects; revision-stamped versions >> are a poor (but acceptable in the near-term) substitute. > > Same here. I'm feeling like I'm not yet understanding what the trunk > will be used like. > >> Tracking the trunk of any dependency is not acceptable: >> it undoes the reason for >> moving the projects out-of-tree in the first place. If we aren't going >> to do release management on the pieces, then for sanity's sake keep them >> in-tree. >> >> Plone's own trunk-based bundles are living proof of the hell that is >> caused by having svn:externals point at non-frozen dependencies. > > Ah. I don't have any experience with those. What would the trunk of the > Zope 3 tree look like then during development cycles? When do updates on > the externals in the Zope 3 trunk happen?
Typically whenever somebody who knows both "decides" that the satellite has changes which need pulling into Z3; at the latest, they get updated when doing a Z3 release, I would guess. This is like what happens now with ZODB, etc., or with Zope3 as an external in Zope2. I think we are headed to a place where much less "trunk-like" development, except for things which have not yet (or maybe ever) been spun off into satellite projects. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGOmDp+gerLs4ltQ4RAtYzAJ9E7W9Ate0Ntr1rSxP28wcuk+gROACgrR+g 2HDuD9SkZkEWYpPvU5sRqmI= =UCYx -----END PGP SIGNATURE----- _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com