[Zope3-dev] Separating projects
The giant Zope 3 checkout / shadow project dichotomy is driving me up the wall. For code that (really) lives in the Zope 3 checkout, it's difficult to deal with separate releases for the shadow projects since the version number should really come from the Zope 3 project. I'm going to move the code for some projects from the Zope 3 tree into the separate projects, and add externals from Zope 3 to those projects. This will allow releases to be handled more sanely. The projects I'm separating are: zope.index zope.app.catalog zope.app.intid While I move the code and add externals to the Zope 3 tree, checkouts will be momentarily broken. I'll send another note when I'm done with these changes. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Separating projects
Yay! Is this agreed strategy once on is on the wall? :) Christian Am Donnerstag, den 26.04.2007, 14:00 -0400 schrieb Fred Drake: The giant Zope 3 checkout / shadow project dichotomy is driving me up the wall. For code that (really) lives in the Zope 3 checkout, it's difficult to deal with separate releases for the shadow projects since the version number should really come from the Zope 3 project. I'm going to move the code for some projects from the Zope 3 tree into the separate projects, and add externals from Zope 3 to those projects. This will allow releases to be handled more sanely. The projects I'm separating are: zope.index zope.app.catalog zope.app.intid While I move the code and add externals to the Zope 3 tree, checkouts will be momentarily broken. I'll send another note when I'm done with these changes. -Fred -- 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
Re: [Zope3-dev] Separating projects
On 4/26/07, Christian Theune [EMAIL PROTECTED] wrote: Yay! Is this agreed strategy once on is on the wall? I'm not sure I understand you question. I spoke briefly with Jim today about this issue, and he suggests that for packages that really live within the Zope3 project, they need to share version numbers with Zope3. This imposes all sorts of overhead on the various release managers for the different packages. This makes it very difficult to release the satellite projects in a non-synchronized way. For code that really lives in the satellite projects, the satellite projects own the release cycle for that code, and control their own version number. For this reason, it's better to have the code live in the satellite projects, and let the giant checkout use externals for them if it needs to. Since I expect the giant checkout to rapidly fall out of favor, I'm all for moving code to the satellite projects. Then Zope 3 will be free to become a swarm of nano-projects that can be assembled into useful but also lean and maintainable applications. Which is what we really care about. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
