Jim Fulton wrote:
For example, Zope 3 tracks creation and modification times that have
nothing
to do with database time stamps.
I agree. Is there any reason for ZODB to actually keep timestamps rather than
just use serial version ids?
(I understand calls to get the system tiem are expensive,
Lennart Regebro wrote:
From: Casey Duncan [EMAIL PROTECTED]
This is in no way a defense of the release tactics for 2.6.0, but
these types of changes should be done on their own branch and
then merged in atomically to avoid exactly this type of issue.
They were. There were two independant,
Chris McDonough wrote:
FWIW, the reason that there is a flurry of activity before any release
is because people want to see features in a stable release version and
by nature (IMHO) programmers are procrastinators. ;-)
This doesn't fit with normal open source practice. Why are we starting to
Hi,
I have a product that stores customer information in mysql using
ZSQLMethods.
I would like each customer to have a different mysql database (same
structure), but all use the same ZSQLMethods for access.
So, I tried the following:
/ - root contains ZSQLMethods and default DB Connector (seems
Ross J. Reedstrom wrote:
It what world do you live, and can I move there? Every large open source
project I've particpated in or kept track of has had this problem - it's
_really hard_ to turn down cool new patches just because your supposed to
be in feature freeze, trying to get a stable
I submitted 2 features to 2.6,
gzip compression
ftp pasv port range spec
the first one made it, the 2nd one didn't.
Both are listed as comitted and vetted on
http://dev.zope.org/Wikis/DevSite/Projects/Zope2.6/ProposedFeatures
But the passive port range patch didn't make it into 2.6
Oliver Bleutgen writes:
...
What do _you_ think 'normal open source practice' is?
FWIW, see as an example
http://developer.kde.org/development-versions/kde-3.0-release-plan.html
and/or
http://developer.kde.org/development-versions/kde-3.2-features.html
Seems to work
Jeff Coleman writes:
I have a product that stores customer information in mysql using
ZSQLMethods.
I would like each customer to have a different mysql database (same
structure), but all use the same ZSQLMethods for access.
So, I tried the following:
/ - root contains ZSQLMethods and
