Re: [Zope-dev] Mountpoints
There is a wrinkle about performing this merge that eluded my memory until now. To support multidatabases within Zope, it was reasonable to change ZODB.config.ZODBDatabase to support the heretofore likely-unused-by-real-world-code "databases" and "database_name" options that may now be passed into ZODB.DB's constructor: http://svn.zope.org/ZODB/branches/blob-merge-branch/src/ZODB/config.py?rev=38626&r1=38574&r2=38626 The current blob-merge-branch code depends on this change being available in the ZODB revision it uses. In case you're interested, the code that actually makes use of this feature in the zodb-blobs-branch is in the Zope2.datatypes.DBTab.getDatabase method. Is this change acceptable for a merge into the ZODB HEAD? - C On Wed, 2005-10-19 at 01:02 -0400, Chris McDonough wrote: > On Tue, 2005-10-18 at 22:21 -0400, Tim Peters wrote: > > [Chris McDonough] > > > I think I may need some remedial SVN help because I don't want to do > > > this in a stupid way. Hopefully someone will be willing to guide me > > > through this. > > > > I'll be in FB tomorrow if you'd like to pair on it (while in theory > > Jim might object, I think he thinks getting this done is important > > enough to offer real help -- especially if he doesn't have to offer it > > himself ). > > Thanks for the offer! I won't be able to visit ZC world HQ tomorrow, > though unless you'd be there and willing to start around 10pm. "Other > duties" is my official excuse but I'm also horrified by the idea that > I'd be expected to wear pants if I came over there. That's just > uncivilized. :-) > > > > The zodb-blobs-branch contains code that use Tim's multidatabase support > > > for mountpoint support rather than the older DBTab code which > > > monkeypatched ZODB and did other nasty things. It contains a few other > > > ancillary changes that make it possible to use a HEAD-ish ZODB package > > > in Zope 2 as well (including changes to the setup.py I mentioned which > > > allows a newer ZODB to be compiled). > > > > Check. Question: does zodb-blobs-branch contain anything you _don't_ > > want to see on Zope trunk now? You didn't mention anything like that > > here. > > No (save for inappropriate svn:externals to ZODB and ZEO). > > > > - merge the changes that have happened since September 25 on the > > > Zope 2 trunk into the mountpoint-merge-branch > > > > Why? It may create headaches and I don't see the attraction. Have > > people been checking in changes to the same files over the last 3 > > weeks? Even if they have, conflicts are probably easier to deal with > > when the new branch gets merged back to the trunk. > > No, people haven't been changing the same files (except for maybe > setup.py) so seems like good advice. This is really what I needed to > understand. > > > > But I've read the Zope SVN FAQ and it frowns on the practice of merging > > > trunk changes into a branch and back again. > > > > That's because it's so easy to lose track of what you're doing then. > > It probably can't be avoided on very long-lived branches, but this > > branch is only several weeks old now, right? > > Yes. The zodb-blobs-branch can just die after this merge if there's a > way to get delete branches entirely. If there is to be a long-lived > branch, it will be the "blob-merge-branch" of ZODB. > > Given that Zope 2.9 is not going to ship with blob support due to > feature freeze, I think this means that we have until May to allow the > blob-merge-branch to get utterly out of sync with the ZODB trunk. We > can then easily wait until, say, the last week in April to worry about > issues caused by that desynchronization. The work necessary to remerge > should provide just the appropriate amount of delay to allow blobs to > miss the next major Zope release. ;-) > > > > Also, what is the "right" branch of ZODB to use in the svn:external for > > > lib/python/ZODB so I can test that it all works ok before I actually > > > perform the merge to the HEAD? > > > > I never leave a Zope pointing at a ZODB branch -- only at a ZODB tag. > > The only two suitable tags at this time are > > > > ZODB/tags/3.5.1 > > and > > ZODB/tags/3.6.0a4 > > > > Either should work fine for you. If you use the latter, it may save > > me some time later ;-) But in either case, it won't last long (I'll > > have to stitch in a 3.5.2 beta or 3.6.0 beta soon anyway, and tags for > > those don't exist now). > > Great, that's what I needed to know. > > Thanks Tim! > > - C > > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HT
Re: [Zope-dev] Mountpoints
On Tue, 2005-10-18 at 22:21 -0400, Tim Peters wrote: > [Chris McDonough] > > I think I may need some remedial SVN help because I don't want to do > > this in a stupid way. Hopefully someone will be willing to guide me > > through this. > > I'll be in FB tomorrow if you'd like to pair on it (while in theory > Jim might object, I think he thinks getting this done is important > enough to offer real help -- especially if he doesn't have to offer it > himself ). Thanks for the offer! I won't be able to visit ZC world HQ tomorrow, though unless you'd be there and willing to start around 10pm. "Other duties" is my official excuse but I'm also horrified by the idea that I'd be expected to wear pants if I came over there. That's just uncivilized. :-) > > The zodb-blobs-branch contains code that use Tim's multidatabase support > > for mountpoint support rather than the older DBTab code which > > monkeypatched ZODB and did other nasty things. It contains a few other > > ancillary changes that make it possible to use a HEAD-ish ZODB package > > in Zope 2 as well (including changes to the setup.py I mentioned which > > allows a newer ZODB to be compiled). > > Check. Question: does zodb-blobs-branch contain anything you _don't_ > want to see on Zope trunk now? You didn't mention anything like that > here. No (save for inappropriate svn:externals to ZODB and ZEO). > > - merge the changes that have happened since September 25 on the > > Zope 2 trunk into the mountpoint-merge-branch > > Why? It may create headaches and I don't see the attraction. Have > people been checking in changes to the same files over the last 3 > weeks? Even if they have, conflicts are probably easier to deal with > when the new branch gets merged back to the trunk. No, people haven't been changing the same files (except for maybe setup.py) so seems like good advice. This is really what I needed to understand. > > But I've read the Zope SVN FAQ and it frowns on the practice of merging > > trunk changes into a branch and back again. > > That's because it's so easy to lose track of what you're doing then. > It probably can't be avoided on very long-lived branches, but this > branch is only several weeks old now, right? Yes. The zodb-blobs-branch can just die after this merge if there's a way to get delete branches entirely. If there is to be a long-lived branch, it will be the "blob-merge-branch" of ZODB. Given that Zope 2.9 is not going to ship with blob support due to feature freeze, I think this means that we have until May to allow the blob-merge-branch to get utterly out of sync with the ZODB trunk. We can then easily wait until, say, the last week in April to worry about issues caused by that desynchronization. The work necessary to remerge should provide just the appropriate amount of delay to allow blobs to miss the next major Zope release. ;-) > > Also, what is the "right" branch of ZODB to use in the svn:external for > > lib/python/ZODB so I can test that it all works ok before I actually > > perform the merge to the HEAD? > > I never leave a Zope pointing at a ZODB branch -- only at a ZODB tag. > The only two suitable tags at this time are > > ZODB/tags/3.5.1 > and > ZODB/tags/3.6.0a4 > > Either should work fine for you. If you use the latter, it may save > me some time later ;-) But in either case, it won't last long (I'll > have to stitch in a 3.5.2 beta or 3.6.0 beta soon anyway, and tags for > those don't exist now). Great, that's what I needed to know. Thanks Tim! - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
On Tue, 2005-10-18 at 11:32 -0400, Jim Fulton wrote: > Ah, I had forgotten about that. It would be great to merge the mountpoint > work into the head. There isn't a 2.9 branch afaik. I think I may need some remedial SVN help because I don't want to do this in a stupid way. Hopefully someone will be willing to guide me through this. There exists a branch of the Zope 2 trunk named the zodb-blobs-branch. It was created as a branch of the Zope 2 trunk on September 25 (about 3 weeks ago). The zodb-blobs-branch contains code that use Tim's multidatabase support for mountpoint support rather than the older DBTab code which monkeypatched ZODB and did other nasty things. It contains a few other ancillary changes that make it possible to use a HEAD-ish ZODB package in Zope 2 as well (including changes to the setup.py I mentioned which allows a newer ZODB to be compiled). The zodb-blobs-branch happens to link in an svn external for the ZODB package which currently points to a *ZODB* branch named "blob-merge-branch". This is really the only thing "blob-ish" about the zodb-blobs-branch. All of the changes that actually cause blobs to be supported are isolated in that ZODB branch. The rest of the changes are really just to support a later ZODB revision within Zope. It's likely that this svn external can be changed to point to any 3.6-ish ZODB branch without breaking things too badly. So I'd *think* I'd like to: - create a SVN branch *from the zodb-blobs-branch* named mountpoint-merge-branch - change the svn external for lib/python/ZODB on the mountpoint-merge-branch to point at the proper ZODB revision - merge the changes that have happened since September 25 on the Zope 2 trunk into the mountpoint-merge-branch - merge the mountpoint-merge-branch back in to the trunk. But I've read the Zope SVN FAQ and it frowns on the practice of merging trunk changes into a branch and back again. Is there a better way to do this other than applying the changes manually to the HEAD? Also, what is the "right" branch of ZODB to use in the svn:external for lib/python/ZODB so I can test that it all works ok before I actually perform the merge to the HEAD? - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
[Chris McDonough] > I think I may need some remedial SVN help because I don't want to do > this in a stupid way. Hopefully someone will be willing to guide me > through this. I'll be in FB tomorrow if you'd like to pair on it (while in theory Jim might object, I think he thinks getting this done is important enough to offer real help -- especially if he doesn't have to offer it himself ). > There exists a branch of the Zope 2 trunk named the zodb-blobs-branch. > It was created as a branch of the Zope 2 trunk on September 25 (about 3 > weeks ago). Check. > The zodb-blobs-branch contains code that use Tim's multidatabase support > for mountpoint support rather than the older DBTab code which > monkeypatched ZODB and did other nasty things. It contains a few other > ancillary changes that make it possible to use a HEAD-ish ZODB package > in Zope 2 as well (including changes to the setup.py I mentioned which > allows a newer ZODB to be compiled). Check. Question: does zodb-blobs-branch contain anything you _don't_ want to see on Zope trunk now? You didn't mention anything like that here. > The zodb-blobs-branch happens to link in an svn external for the ZODB > package which currently points to a *ZODB* branch named > "blob-merge-branch". This is really the only thing "blob-ish" about the > zodb-blobs-branch. All of the changes that actually cause blobs to be > supported are isolated in that ZODB branch. The rest of the changes are > really just to support a later ZODB revision within Zope. It's likely > that this svn external can be changed to point to any 3.6-ish ZODB > branch without breaking things too badly. FWIW, that sounds likely to me too. > So I'd *think* I'd like to: > > - create a SVN branch *from the zodb-blobs-branch* named > mountpoint-merge-branch Yup. > - change the svn external for lib/python/ZODB on the > mountpoint-merge-branch to point at the proper ZODB revision Likewise. Be sure to do an "svn up" right after (while only a bona fide idiot could make this mistake, on two occasions so far I've switched to a different external, run tests, and checked it in -- only to realize later that I _hadn't_ done "svn up" so didn't actually test anything new -- heh). > - merge the changes that have happened since September 25 on the > Zope 2 trunk into the mountpoint-merge-branch Why? It may create headaches and I don't see the attraction. Have people been checking in changes to the same files over the last 3 weeks? Even if they have, conflicts are probably easier to deal with when the new branch gets merged back to the trunk. > - merge the mountpoint-merge-branch back in to the trunk. Bingo. > But I've read the Zope SVN FAQ and it frowns on the practice of merging > trunk changes into a branch and back again. That's because it's so easy to lose track of what you're doing then. It probably can't be avoided on very long-lived branches, but this branch is only several weeks old now, right? > Is there a better way to do this other than applying the changes manually > to the HEAD? I'm not sure what this means. As above, my natural inclination is not to try merging anything in the trunk -> branch direction here. > Also, what is the "right" branch of ZODB to use in the svn:external for > lib/python/ZODB so I can test that it all works ok before I actually > perform the merge to the HEAD? I never leave a Zope pointing at a ZODB branch -- only at a ZODB tag. The only two suitable tags at this time are ZODB/tags/3.5.1 and ZODB/tags/3.6.0a4 Either should work fine for you. If you use the latter, it may save me some time later ;-) But in either case, it won't last long (I'll have to stitch in a 3.5.2 beta or 3.6.0 beta soon anyway, and tags for those don't exist now). ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
Note that I wormed my way around the new ZODB compilation issues by changing the setup.py file on the zodb-blobs-branch (a minor tweak of the Zope HEAD).. here's the comment I left to myself. # added . to EXTENSIONCLASS_INCLUDEDIRS in order to be able to compile # ZODB HEAD code (which uses qualified paths to find header files). # This # should be a temporary change, thrown away once we use zpkg to package # Zope. EXTENSIONCLASS_INCLUDEDIRS = ['ExtensionClass', '.'] - C On Tue, 2005-10-18 at 16:18 -0400, Fred Drake wrote: > [It doesn't look like my response went to the zope-dev list; re-sending.] > > On Tuesday 18 October 2005 15:43, Tim Peters wrote: > > I'm copying Fred because he may remember more about this than I do. > > Fred, do you know of a reason why I can't stitch a newer ZODB into > > Zope(2) trunk? I have a dim, fading memory of the last attempt > > failing, and of agreeing in email to wait for the "5 guys" to "do > > something" before trying again. Sorry for not being more specific ... > > We need to do the zpkg/ZODB switch all at once because it affects how > extensions get their include files. When I tried switching the Zope 2 trunk > before, there was a problem due to Five tests failing. I don't remember the > details, but the Five-folks seemed to think things would be better with newer > versions of Five. > > Since Five development is done elsewhere, though, it's hard to tell what the > deal is with that. I snapshotted what I did get done as the > zpkg-build-branch, so we can get back to it without duplicating work. > > > -Fred > > -- > Fred L. Drake, Jr. > "Society attacks early, when the individual is helpless." --B.F. Skinner > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Five status on Zope trunk (was Re: Mountpoints)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Peters wrote: > [Tim] > >>>I'm copying Fred because he may remember more about this than I do. >>>Fred, do you know of a reason why I can't stitch a newer ZODB into >>>Zope(2) trunk? I have a dim, fading memory of the last attempt >>>failing, and of agreeing in email to wait for the "5 guys" to "do >>>something" before trying again. Sorry for not being more specific ... > > > [Fred] > >>We need to do the zpkg/ZODB switch all at once because it affects how >>extensions get their include files. > > > Aha! That vaguely rings another vague bell ;-) The ZODB 3.5+ source > code spells "#include" in its C files in a different way, and that > can't work with the way Zope trunk is currently built. > > >>When I tried switching the Zope 2 trunk before, there was a problem due >>to Five tests failing. I don't remember the details, but the Five-folks >>seemed to think things would be better with newer versions of Five. >> >>Since Five development is done elsewhere, though, it's hard to tell what the >>deal is with that. > > > Can anyone working on Five comment here, please? I gather that the > first 2.9 beta release occurs in 2 weeks, and if Fred can't do his > zpkgtools work, I can't update the trunk to a newer ZODB, and then > Chris McDonough can't do his rework of mount points (the original > topic of this thread), and then (best case) the world economy > collapses. What are we blocked on? I know we expect to land a new version of Five (1.3), which will be compatible with Zope 3.1+; what I don't know is why ZODB work is blocked on that. Does the new ZODB stuff expect newer stuff from Zope3 than is currently on the Zope2 trunk? Or does the new ZODB stuff break backward compatibility somehow? >>I snapshotted what I did get done as the zpkg-build-branch, so we can get >>back to it without duplicating work. > > > So there's no reason yet to be depressed ;-) Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDVWUv+gerLs4ltQ4RAgEWAJwPNhJOEyAnvYaze6PY++k0+uHN9wCePkat JupUuemkgbtNqT3Z/na+Mcc= =MsOB -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Five status on Zope trunk (was Re: [Zope-dev] Mountpoints)
[Tim] >> I'm copying Fred because he may remember more about this than I do. >> Fred, do you know of a reason why I can't stitch a newer ZODB into >> Zope(2) trunk? I have a dim, fading memory of the last attempt >> failing, and of agreeing in email to wait for the "5 guys" to "do >> something" before trying again. Sorry for not being more specific ... [Fred] > We need to do the zpkg/ZODB switch all at once because it affects how > extensions get their include files. Aha! That vaguely rings another vague bell ;-) The ZODB 3.5+ source code spells "#include" in its C files in a different way, and that can't work with the way Zope trunk is currently built. > When I tried switching the Zope 2 trunk before, there was a problem due > to Five tests failing. I don't remember the details, but the Five-folks > seemed to think things would be better with newer versions of Five. > > Since Five development is done elsewhere, though, it's hard to tell what the > deal is with that. Can anyone working on Five comment here, please? I gather that the first 2.9 beta release occurs in 2 weeks, and if Fred can't do his zpkgtools work, I can't update the trunk to a newer ZODB, and then Chris McDonough can't do his rework of mount points (the original topic of this thread), and then (best case) the world economy collapses. > I snapshotted what I did get done as the zpkg-build-branch, so we can get > back to it without duplicating work. So there's no reason yet to be depressed ;-) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
[It doesn't look like my response went to the zope-dev list; re-sending.] On Tuesday 18 October 2005 15:43, Tim Peters wrote: > I'm copying Fred because he may remember more about this than I do. > Fred, do you know of a reason why I can't stitch a newer ZODB into > Zope(2) trunk? I have a dim, fading memory of the last attempt > failing, and of agreeing in email to wait for the "5 guys" to "do > something" before trying again. Sorry for not being more specific ... We need to do the zpkg/ZODB switch all at once because it affects how extensions get their include files. When I tried switching the Zope 2 trunk before, there was a problem due to Five tests failing. I don't remember the details, but the Five-folks seemed to think things would be better with newer versions of Five. Since Five development is done elsewhere, though, it's hard to tell what the deal is with that. I snapshotted what I did get done as the zpkg-build-branch, so we can get back to it without duplicating work. -Fred -- Fred L. Drake, Jr. "Society attacks early, when the individual is helpless." --B.F. Skinner ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] New mailinglist for Zope 3 translators
Hello all, [Sorry for the cross-post, please CC replies to zope3-i18n@zope.org only.] two months ago, I started an initiative [1] to translate Zope 3.1 using Ubuntu's Launchpad system [2]. Since then, I've received a lot of emails from numerous volunteers around the world and many of them made some excellent progress [3]. Thanks to everyone who contributed so far. A new mailinglist at zope3-i18n@zope.org will now help translators and developers like me to coordinate their work. For example, all those translations will have to be integrated back into the Zope 3.1 repository at some point which has to be coordinated somehow. Also, translators themselves will want to coordinate the work among them. The mailinglist will serve as a forum for discussing and coordinating things like that. So, if you're involved into Zope 3 translations OR if you would like to contribute something to Zope 3 by helping to translate it into your language, please subscribe to the new list [4]. If you have any questions, feel free to email me or even better the new list. Best regards Philipp [1] http://mail.zope.org/pipermail/zope3-dev/2005-August/015113.html [2] https://launchpad.net [3] https://launchpad.net/products/zope/+series/zope3.1/+pots/zope [4] http://mail.zope.org/mailman/listinfo/zope3-i18n ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
[Chris McDonough] >> This is already done on the zodb-blobs-branch. I would be happy to >> create a mountpoint-branch that does not externally link the ZODB with >> blob support, then merge the changes in to the Zope 2 HEAD (and 2.9 >> branch if one exists). [Jim Fulton] > Ah, I had forgotten about that. It would be great to merge the mountpoint > work into the head. There isn't a 2.9 branch afaik. FYI, there's a problem with that: Zope trunk (2.9) is still using ZODB 3.4, and multi-databases weren't introduced before ZODB 3.5. The _intent_ has been that 2.9 would use ZODB 3.5 or even 3.6, but that got hung up due to problems with switching the "5 integration" part to use zpkgtools. I'm copying Fred because he may remember more about this than I do. Fred, do you know of a reason why I can't stitch a newer ZODB into Zope(2) trunk? I have a dim, fading memory of the last attempt failing, and of agreeing in email to wait for the "5 guys" to "do something" before trying again. Sorry for not being more specific ... ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
[Chris McDonough] >>> This is already done on the zodb-blobs-branch. I would be happy to >>> create a mountpoint-branch that does not externally link the ZODB with >>> blob support, then merge the changes in to the Zope 2 HEAD (and 2.9 >>> branch if one exists). [Jim Fulton] >> Ah, I had forgotten about that. It would be great to merge the mountpoint >> work into the head. There isn't a 2.9 branch afaik. FYI, Zope trunk (in SVN) is current 2.9 development. [Chris] > OK, I will do so. In that case, I'm willing to share this set of probably-related open Collector issues: ZODBMountPoint should not monkey-patch ZODB http://www.zope.org/Collectors/Zope/1525 Clean up mounts, TemporaryFolder http://www.zope.org/Collectors/Zope/1800 ZODB: Mounting broken for non default transaction manager http://www.zope.org/Collectors/Zope/1875 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] svn.zope.org borked?
[Andreas Jung] > all changes I made for the last hotfix release (patch for the reST .. > include problem) have disappeared from the SVN (both from 2.8 branch and > the trunk). Are you sure? The SVN log on Zope trunk shows what I guess are the relevant checkins, revs 39013 and 39014, on 2005-10-09, both with checkin comment update to docutils 0.3.9 If that's it, they appear to be there. There is a problem with them, though: the svn:eol-style property isn't set to "native" on any of the files added by these checkins, so they look like gibberish under many Windows tools (and, e.g., windiff thinks every line differs between the SVN Zope trunk and CVS Zope 2.7 branch copies of docutils). While Python doesn't care (Linux-style .py files work fine on Windows), that should get fixed. > ... > Is there something broken with the SVN database? Maybe, but don't see any real evidence of that yet. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] svn.zope.org borked?
Forget my mail. I was looking at the wrong terminal :-/ Andreas --On 18. Oktober 2005 18:04:32 +0200 Andreas Jung <[EMAIL PROTECTED]> wrote: Hi, all changes I made for the last hotfix release (patch for the reST .. include problem) have disappeared from the SVN (both from 2.8 branch and the trunk). I am *pretty sure* that I commited all changes. Is there something broken with the SVN database? Andreas pgpByt9xcwiNC.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] svn.zope.org borked?
Hi, all changes I made for the last hotfix release (patch for the reST .. include problem) have disappeared from the SVN (both from 2.8 branch and the trunk). I am *pretty sure* that I commited all changes. Is there something broken with the SVN database? Andreas pgpyTk6g73p0z.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
On Tue, 2005-10-18 at 11:32 -0400, Jim Fulton wrote: > Chris McDonough wrote: > > This is already done on the zodb-blobs-branch. I would be happy to > > create a mountpoint-branch that does not externally link the ZODB with > > blob support, then merge the changes in to the Zope 2 HEAD (and 2.9 > > branch if one exists). > > Ah, I had forgotten about that. It would be great to merge the mountpoint > work into the head. There isn't a 2.9 branch afaik. OK, I will do so. > > November 1 feature freeze, eh? > > Yup. :) > > > I'd love to get blobs in before this too > > but I don't know if it will be possible. > > I don't think so. Nov 1 is less than 2 weeks away. I think > we need to be realistic. Yep. We'll wait on it then. - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Reminder: feature freeze November 1.
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: This is a reminder that there will be a feature freeze for the December Zope releases on November 1. No new features for the November releases should be added after October 31. The Zope trunks should be stable and ready for a beta release on November 1. We are committed to time-based releases. This means we need to be very disciplined about deadlines. If a cool new feature isn't quite ready before November 1, then it could be be included in the June release, for which the feature freeze will be May 1. Cool. I like the way the Ubuntu guys describe their freeze / process: http://lists.ubuntu.com/archives/ubuntu-devel/2005-February/004077.html I don't know what would qualify for "release goals" versus "targets of opportunity" for this cycle, though. Me neither. I have a sense that they are being a lot more formal about their process than we are though. Perhaps we should be more formal, but I kind of doubt it. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
Chris McDonough wrote: This is already done on the zodb-blobs-branch. I would be happy to create a mountpoint-branch that does not externally link the ZODB with blob support, then merge the changes in to the Zope 2 HEAD (and 2.9 branch if one exists). Ah, I had forgotten about that. It would be great to merge the mountpoint work into the head. There isn't a 2.9 branch afaik. November 1 feature freeze, eh? Yup. :) > I'd love to get blobs in before this too but I don't know if it will be possible. I don't think so. Nov 1 is less than 2 weeks away. I think we need to be realistic. I would definately want to review this before it got merged into the head. I think Tim might too. I don't think it's ready for my review yet. Anyway, if you want to make this a priority, I'm willing to make time for review as best I can. If you want to try to finish this before Nov 1, I'll try to help by doing timely reviews. Note that this will be of limited usefulness without also updating Zope file implementations (z2 and z3) to take advantage of it, although people could build add-on packages that used it. If not, it would really suck. Well, I dunno, if it's not ready, June is not that far away. I'm confident that we could get this done by the May 1 feature freeze if this was a priority. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mountpoints
This is already done on the zodb-blobs-branch. I would be happy to create a mountpoint-branch that does not externally link the ZODB with blob support, then merge the changes in to the Zope 2 HEAD (and 2.9 branch if one exists). November 1 feature freeze, eh? I'd love to get blobs in before this too but I don't know if it will be possible. If not, it would really suck. On Tue, 2005-10-18 at 10:22 -0400, Jim Fulton wrote: > I was just reminded (by a zope3-dev question) of mount points. > Zope2 has a mount-point capability that requires baboon patching > of ZODB. The ZODB that will be used for Zope 2.9 has a multi-database > feature that would allow a much simpler Zope 2 mount implementation that > would not require even monkey patching of ZODB. It also, I think, > would provide much more robust mounting behavior. It would be great > if someone would update mounting for Zoep 2.9 to use multi-databases. > I'd be happy to provide advice for such an effort. Of course, this > would need to be completed before the November 1 feature freeze. > > Jim > ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Mountpoints
I was just reminded (by a zope3-dev question) of mount points. Zope2 has a mount-point capability that requires baboon patching of ZODB. The ZODB that will be used for Zope 2.9 has a multi-database feature that would allow a much simpler Zope 2 mount implementation that would not require even monkey patching of ZODB. It also, I think, would provide much more robust mounting behavior. It would be great if someone would update mounting for Zoep 2.9 to use multi-databases. I'd be happy to provide advice for such an effort. Of course, this would need to be completed before the November 1 feature freeze. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Reminder: feature freeze November 1.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: > > This is a reminder that there will be a feature freeze for the December > Zope releases on November 1. No new features for the November releases > should > be added after October 31. The Zope trunks should be stable and ready > for a beta > release on November 1. > > We are committed to time-based releases. This means we need to be very > disciplined about deadlines. If a cool new feature isn't quite > ready before November 1, then it could be be included in the June > release, for which the feature freeze will be May 1. Cool. I like the way the Ubuntu guys describe their freeze / process: http://lists.ubuntu.com/archives/ubuntu-devel/2005-February/004077.html I don't know what would qualify for "release goals" versus "targets of opportunity" for this cycle, though. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDVN/m+gerLs4ltQ4RAnc2AJ9zcULEgze+3to3Iqmy5xU2QAisfwCfSzy3 4r40IYdK4ytScTAXObp3cgk= =hzGm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Reminder: feature freeze November 1.
This is a reminder that there will be a feature freeze for the December Zope releases on November 1. No new features for the November releases should be added after October 31. The Zope trunks should be stable and ready for a beta release on November 1. We are committed to time-based releases. This means we need to be very disciplined about deadlines. If a cool new feature isn't quite ready before November 1, then it could be be included in the June release, for which the feature freeze will be May 1. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
