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
-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
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
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
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
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
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
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
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
[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,
[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.
[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 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,
[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
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
-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
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
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
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
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
20 matches
Mail list logo
