-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all (and especially Lennart),
I need a quick sanity check. Trying to test a package of mine for Python
3 compatibility I built Python 3.1.2 and installed distribute into it.
My package depends on zope.interface. I am executing...
$ python3.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/2/10 21:30 , Lennart Regebro wrote:
On Sun, May 2, 2010 at 18:37, Jens Vagelpohl j...@dataflake.org wrote:
The issue is a non-ASCII character in the Changelog:
snip
- - Added support for Python 3.1. Contributors:
Lennart Regebro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft?
Like 5 years old nothing happened since then bugs.
I think we should add a tag too old, add a note to warn subscribers,
then set a status
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/22/10 11:11 , Adam GROSZER wrote:
Hello,
JV On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft?
Like 5 years old nothing happened since then bugs.
I think we should add a tag too old,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/15/10 09:58 , Tres Seaver wrote:
Sidnei da Silva wrote:
+link = ('https://bugs.launchpad.net/%s/+bug/%s'
+% (self.project_name, bug_id))
You can actually link to the bug having an id only, by using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 17:08 , Tres Seaver wrote:
I'm seeing frequent periods of 50+% packet loss to the machine, and
can't even get top to run on it this morning. Any clues about what is
causing the load?
I haven't watched it because I don't know when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 17:27 , Jim Fulton wrote:
We've been having some networking issues over the last week or two that
we believe to have been addressed.
I'm still getting alerts from Nagios 2-3 times a day caused by high
packet loss and inability to connect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/18/10 09:23 , Godefroid Chapelle wrote:
As far as I know, Zope 2 has no release manager since Andreas retired
after so many years of hard work.
I think there is a need for a new release manager.
Is that question part of the horizon of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/10/10 15:53 , Lennart Regebro wrote:
On Tue, Feb 9, 2010 at 08:19, Marius Gedminas mar...@gedmin.as wrote:
Well, technically I suppose we're all violating the law by not following
the ZPL requirement of keeping the licence text next to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/24/10 13:08 , Baiju M wrote:
Hi,
I would like to know the legal formalities required
to accept a logo (with special font).
Also I would like to know the same for web design.
Is there any guideline for Zope Foundation ?
BlueBream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andreas,
I would like to inform you that I intent to retreat from the Zope 2
release manager position soon. I have been serving the Zope community in
this position for almost seven years and now it is time to move on and
hand
over the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Jan Ulrich Hasecke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.10 08:36, Martin Aspeli wrote:
+1. It puts the final nail in the Zope 3 coffin and allows a reborn
vampire to emerge from slumber.
Ok, we all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hey Tres,
Tres Seaver wrote:
You're kidding, right?
[snip]
My self-interest? Not really: you are appealing to my altruism, in the
fact that I care about the *broader* Zope community (broader than Zope2,
Grok,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shane Hathaway wrote:
Jan Ulrich Hasecke wrote:
On 04.01.10 19:23, Baiju M wrote:
Hi All,
I am proposing to call Zope 3 - the web frame work
as BlueBream. The main use for name is documentation.
Coming from marketing I strongly suggest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
Hi there,
we have some huge ZODB file storage (60-80 GB each) and we want
to split the storage into a number of smaller storage (easier
to handle for backup and packing). The storages themselves only
contain a few (Zope 2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
We have three perspectives:
* the ZTK is new, therefore the ZTK doesn't need to care about Zope 3 at
all.
+1
* the ZTK is a renamed, refocused Zope 3, therefore the ZTK needs to
care about Zope 3.
- -1
* both: the
On Oct 15, 2009, at 19:02 , Baiju M wrote:
Hi Jens,
In Zope 2.12, we have given a link to :
http://docs.zope.org/zope2book/
from the main page displayed after installation (index_html).
It's redirecting to old page which we have changed few days
back. Can you please change the
On Oct 10, 2009, at 06:22 , Baiju M wrote:
Hi Jens,
I was looking at Zope 2 documentation. To generate this
site :
http://docs.zope.org/zope2/
we use the buildout available here, is it ?
svn://svn.zope.org/repos/main/zope2docs/trunk
Yes.
So, can I remove the buildout
On Oct 10, 2009, at 11:15 , Baiju M wrote:
Also where I need to make change to fix docs.zope.org
I will make those. That front page is not in SVN anywhere, it's just
one file on the file system.
jens
smime.p7s
Description: S/MIME cryptographic signature
On Oct 10, 2009, at 11:15 , Baiju M wrote:
Also I removed the 'sources' directory and moved all docs one level
up.
This will shorten the URL. But now I realized that it's going
to break few URLs in these places:
http://docs.zope.org/
http://zope2.zope.org/resources/documentation
Should I
On Sep 21, 2009, at 18:47 , Martijn Faassen wrote:
So, I'd be against any you can't contribute documentation unless it's
executable rule. The value of narrative documentation is tremendous,
automatically checked or not. Hopefully there are also iterative
ways to
get from non-executable to
On Sep 9, 2009, at 15:30 , Martijn Faassen wrote:
Ah, I perhaps misunderstood. I figured the resolving of relative
externals would be a problem with a Subversion 1.4.x client.
There's two different issues being confused here.
SVN 1.4 clients will work with SVN 1.5 repositories in general.
On Sep 9, 2009, at 15:59 , Sidnei da Silva wrote:
On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohlj...@dataflake.org
wrote:
SVN 1.4 clients will work with SVN 1.5 repositories in general.
However,
that's not the real issue here. The issue is the new-style externals
definitions that
On Sep 9, 2009, at 17:05 , Martijn Faassen wrote:
Jens Vagelpohl wrote:
SVN 1.4 clients will work with SVN 1.5 repositories in general.
However,
that's not the real issue here. The issue is the new-style externals
definitions that allow you to use relative paths. Those relative
paths
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 15, 2009, at 19:03 , Alec Mitchell wrote:
There's one additional significant change to Zope behavior here that
I forgot to mention. The current implementation sets the python
default email transfer and header encoding for 'utf-8'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 14, 2009, at 06:22 , Alec Mitchell wrote:
It would be very helpful to have these changes in Zope 2.12;
otherwise, Plone 4.0 will be stuck with our unmaintained
SecureMailHost product for yet another release in order to provide
equivalent
On Aug 13, 2009, at 5:12, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 for the approach in general (I haven't looked at the patch in
detail). Assuming all tests pass, and that you have a test
exercising
the ':' bug you describe, I would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
This is a heads-up that affects anyone accessing the SVN repositories
using the svn:// protocol (so it does not affect anyone accessing SVN
over HTTP, or svn+ssh):
So far the svn service was run through xinetd. We had recurring
will be removed for those who have not
sent in the new agreement.
Thanks again for your support!
Jens Vagelpohl
Secretary, Zope Foundation Board of Directors
[1] http://foundation.zope.org/agreements/ZopeFoundation_Committer_Agreement
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2009, at 19:01 , Wichert Akkerman wrote:
Are you sending receipt confirmations? I submitted an updated
agreement
a while ago, but never got a response, so I am unsure at the moment if
it was received or if I still need to take
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 28, 2009, at 13:08 , Martijn Faassen wrote:
What do people think about:
* the idea of renaming Site to Locus
I think that's a terrible name. While site at least means something
to people, locus doesn't carry any meaning in the specific
will try to contact any contributor who
has not replied at that point between June 18 and June 26, and
on June 26 checkin access will be removed for those who have not
sent in the new agreement.
Thanks again for your support!
Jens Vagelpohl
Secretary, Zope Foundation Board of Directors
[1] http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 16, 2009, at 23:01 , Wichert Akkerman wrote:
Previously Sidnei da Silva wrote:
Now for another question: how do people feel about moving Zope 3 and
CMF bugs to a similar setup. That is, bug mail goes to a separate
mailing list instead of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 17, 2009, at 22:53 , Sidnei da Silva wrote:
On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl j...@dataflake.org
wrote:
Same here. There is no reason for yet another mailing list. I see it
as needlessly duplicating what Launchpad already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 5, 2009, at 15:58 , Andreas Jung wrote:
Hi there,
I tagged and released Zope 2.12.0 beta 1 today (basically identical
with the latest alpha but it includes ZODB 3.9.0 beta 1).
I'm trying to install the Zope2 egg (pulles in as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 5, 2009, at 17:23 , Andreas Jung wrote:
Unfortunately I can't get SVN 1.5 get working on my Mac.
SVN 1.5 from Fink works perfectly fine here.
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2009, at 12:00 , Jürgen Herrmann wrote:
/home/xlhost/zope/lib/python2.4/site-packages/
Products.CMFCore-2.1.2-py2.4.egg/Products/CMFCore/interfaces/
__init__.py,
line 47, in ?
from Interface.bridge import createZope3Bridge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 2, 2009, at 09:27 , Andreas Jung wrote:
Hi,
I tried several times to update my SVN checkouts (on different
machines). After
updating some svn:exernals, svn fails with something like
svn: warning: Error handling externals definition for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2009, at 17:47 , Andreas Jung wrote:
On 01.05.2009 17:33 Uhr, Chris Withers wrote:
Andreas Jung wrote:
We would have to maintain four different major release of Zope:
2.10, 2.11, 2.12 and 2.13.
Why? I suspect most of this work is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 25, 2009, at 20:30 , Laurence Rowe wrote:
Hi,
I've added the ZODB developers guide to the zope2docs buildout
(converting it to rst) and added another article and some more links
to
the zodb articles section, but ideally these should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2009, at 06:52 , Andreas Jung wrote:
Am 23.04.2009 um 22:23 schrieb Jens Vagelpohl:
On Apr 23, 2009, at 20:13 , Andreas Jung wrote:
Does anyone know about the procedure for uploading stuff to
download.zope.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2009, at 09:49 , Chris Withers wrote:
Tres Seaver wrote:
Is it really the case that no-one knows what's going on here?
Maybe nobody else cares enough to do the debugging you're too lazy
to do? ;)
Tres,
That's not exactly fair.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2009, at 16:35 , Chris Withers wrote:
Jens Vagelpohl wrote:
Sorry Chris, but that's exactly the method you use every single time.
You complain very loudly and expect others to come to your help and
fix stuff without doing any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 23, 2009, at 11:57 , Lacko Roman wrote:
Hi,
Could someone explain me what that message means ?
This simply means that during a moderation queue cleanup of probably
100 (mostly spam) messages to the foundation-info list your post was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 23, 2009, at 20:13 , Andreas Jung wrote:
Does anyone know about the procedure for uploading stuff to
download.zope.org?
Stephan Richter is maintaining the contents of download.zope.org with
a series of scripts that do a simple PyPI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 2, 2009, at 22:53 , Tres Seaver wrote:
+1 to making svn-over-http read-only checkouts work.
This is now working. The repository can be reached under...
http://svn.zope.org/repos/main/
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 10, 2009, at 17:37 , Roger Ineichen wrote:
svn co -r 93260
svn://svn.zope.org/repos/main/zc.table/trunk/src/zc/table zc.table
fails for me with:
svn: Connection closed unexpectedly
(tried from different countries)
I have that problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2009, at 16:32 , Martijn Faassen wrote:
Thanks for pointing that out. If we moved it could you put a
redirect in
place that just pointed .../zope3docs to .../zopeframework?
I think to get started on the move we could copy the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2009, at 18:24 , Jens Vagelpohl wrote:
Let's do this:
- svn copy zope3docs to zopeframework
- once you think zopeframework is ready for public viewing, let me
know and I'll set up a self-updating sandbox and a redirect
- after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2009, at 17:55 , Martijn Faassen wrote:
Jens, could you pick up zopeframework/trunk now for
http://docs.zope.org/zopeframework? And put a redirect in place for
http://docs.zope.org/zope3docs to the new location?
We can then retire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2009, at 19:08 , Martijn Faassen wrote:
Hey,
Jens Vagelpohl wrote:
On Mar 5, 2009, at 17:55 , Martijn Faassen wrote:
Jens, could you pick up zopeframework/trunk now for
http://docs.zope.org/zopeframework? And put a redirect in place
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 5, 2009, at 08:24 , Christian Theune wrote:
As Dan pointed out, some of those documents are a bit more general
than
Zope Framework, but, then again, they're also more general than Zope
3.
So even for that its better to have them in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My suggestion would be foundation-i...@zope.org, since the ZF is the
publisher of the ZPL at this point.
jens
On Feb 26, 2009, at 12:32 , Baiju M wrote:
Can anyone please verify this change. As it is related to license,
I thought just get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 23, 2009, at 17:58 , Andreas Jung wrote:
- the new.zope.org skins should be removed for docs.zope,org. Since
all/most of the content will be auto-generated through Sphinx it
should be sufficient to adjust the color scheme, putting a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2009, at 08:55 , Andreas Jung wrote:
- - are there any legal issues with the design layout in case we
want to
make modifications? I know that the designer of new.zope.org theme
made some trouble when it came to discussion about the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 16, 2009, at 19:43 , Dieter Maurer wrote:
Andreas Jung wrote at 2009-2-16 19:20 +0100:
...
Please come off it. Either become an active contributor and
participate
in our dictatorship
I will never participate in your dictatorship!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 2, 2009, at 18:32 , Christian Theune wrote:
Nevertheless, you're right about the ease of writing ReST in my own
editor.
What's even better: SVN-based documentation (or buildouts that create
it) can be automated so that the site can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 1, 2009, at 06:54 , Stephan Richter wrote:
On Saturday 31 January 2009, Jens Vagelpohl wrote:
I just need to know what to look for to see if
it's fixed.
Works.
Quick question: How is doenload.zope.org maintained? Shell access? And
who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 31, 2009, at 09:49 , Stephan Richter wrote:
On Saturday 31 January 2009, Stephan Richter wrote:
On Saturday 31 January 2009, Christian Theune wrote:
Darn. The moment I send the mail I realise that Stephan said he'll
move
the URLs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 31, 2009, at 10:06 , Tres Seaver wrote:
If you could provide a little bit more context since I have no idea
how download.zope.org is managed I could look at it. I need to know
what the URLs are that do not work.
Probably the virtualhost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 14:42 , Christian Theune wrote:
wiki.zope.org is down. The hosting centre operator just sent a mail
that they have power outages and the location at which wiki.zope.org
sits is affected.
All services should be restored. One
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 16, 2009, at 18:25 , Hanno Schlichting wrote:
The concept of
giving SVN repositories any kind of quality level aspect failed in the
same way. Dependencies are specified in the setup.py and egg metadata.
Quality is judged by who has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 13, 2008, at 14:42 , Benji York wrote:
I'd like for us to disallow pre-1.5 Subversion clients from making
commits starting one year from now (or sooner if there is consensus).
+1
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 09:10 , Andreas Jung wrote:
In the meantime, we can acknowledge that 2.8 and 2.9 are
retired (no
future work except maybe important security fixes),
+1
and announce that
2.10 will be retired after the 2.12 release:
We
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote:
If I'm not mistaken there was something about every release being
supported two years after its initial release in those discussions.
But time went on, we haven't sticked to a time-based
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 27, 2008, at 13:08 , Roché Compaan wrote:
On Sun, 2008-10-26 at 14:07 -0400, Tres Seaver wrote:
- Plone uses too many indexes, and in particular, uses multiple text
indexes. Having extra indexes around just in case is a sure lose
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 27, 2008, at 13:32 , Roché Compaan wrote:
On Mon, 2008-10-27 at 13:23 +0100, Jens Vagelpohl wrote:
When it comes to integrating anything in Zope itself I'd choose the
latter.
Sure, we're not trying to get this into Zope, we're just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 26, 2008, at 16:37 , Hanno Schlichting wrote:
I'd like to change the egg distribution alone and introduce one
setuptools extra to it. The old tarball distribution would stay the
same.
The standard Zope2 egg install would only include
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 20, 2008, at 14:05 , kevin gill wrote:
Hi,
I need a little help. I checked two packages into svn.zope.org, but
I have
set up the hierarchy incorrectly.
The packages are z3c.rotterdam and z3c.boston. The egg is in the base
folder,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 08:54 , Christian Theune wrote:
Good morning,
My Nagios just alarmed me, that the wiki is down. Anybody around who
can
poke it?
Works fine for me.
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 1, 2008, at 11:06 , Christian Theune wrote:
On Wed, 2008-10-01 at 09:15 +0200, Jens Vagelpohl wrote:
On Oct 1, 2008, at 08:54 , Christian Theune wrote:
Good morning,
My Nagios just alarmed me, that the wiki is down. Anybody around who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 26, 2008, at 17:55 , Behrens, Matt wrote:
I am sort of at my wit's end trying to find out how to work this out,
and I've been sort of absent from Zope-dom for the a few years, so
please forgive me if I've missed an obvious statement
On Aug 15, 2008, at 02:35 , Christophe Combelles wrote:
We should also probably consider waiting a bit more for the new site
(new.zope.org) to come up, but I don't know when it will be
finished. It only
needs some content for zope2, grok, and some other pages.
I don't see the connection
On Aug 14, 2008, at 13:59 , Wichert Akkerman wrote:
Previously Zope Tests Summarizer wrote:
Unknown
---
Subject: Storesonline, Plan for an ecommerce Website.
From: Mister Nice Guy
Date: Wed Aug 13 09:14:30 EDT 2008
URL: http://mail.zope.org/pipermail/zope-tests/2008-August/
On Aug 11, 2008, at 10:07 , Christian Theune wrote:
a) the wiki is down. Can someone please fix this?
Well, it wasn't down like it always was on the old server, Apache just
served an empty page for it. This appears to have been a (unrelated)
Apache configuration. It's fixed now.
jens
On Jul 17, 2008, at 14:02 , Baiju M wrote:
Hi all,
Few weeks back Buildout site become live, Jens Vagelpohl setup
the
site at http://buildout.zope.org/ But I couldn't work further on
the site.
If anyone want contribute to the content please add it here:
svn co svn://svn.zope.org
On Jul 12, 2008, at 09:33 , Mark Hammond wrote:
Well, Zope moved onwards from PAS to PAU and I think Plone should
too,
because:
It seems like just yesterday that PAS offered the promise of being
the nice
clean way forward for authentication, and even offered a path to
Zope3.
I've been
On Jul 12, 2008, at 03:04 , Florian Friesdorf wrote:
On Thu, Jul 10, 2008 at 10:56:19PM +0200, Wichert Akkerman wrote:
The one thing I am missing is: why?
Well, Zope moved onwards from PAS to PAU
Huh? Zope 2 uses PAS. The Zope 3 folks have attempted to come up with
a similar solution,
On Jun 18, 2008, at 20:30 , yuppie wrote:
The current Zope 2 policy doesn't make sure the change history of
unreleased versions is complete. But that's no essential part of
that policy. And working with unreleased versions you might use
subversion anyway.
See, I think that's bad. The
On Jun 19, 2008, at 09:51 , Christian Theune wrote:
On Thu, Jun 19, 2008 at 09:08:54AM +0200, Jens Vagelpohl wrote:
See, I think that's bad. The change log should reflect all changes,
be
it in a released version or from Subversion. Or be it a release
branch
or the trunk.
Please note
On Jun 19, 2008, at 12:32 , yuppie wrote:
There is always *one* well defined current maintenance branch.
Version numbering *does* imply a time line if you ignore old
maintenance branches. It's not hard at all to get this right.
I don't think that assumption holds true. Again, using the
On Jun 19, 2008, at 13:36 , yuppie wrote:
Jens Vagelpohl wrote:
On Jun 19, 2008, at 12:32 , yuppie wrote:
There is always *one* well defined current maintenance branch.
Version numbering *does* imply a time line if you ignore old
maintenance branches. It's not hard at all to get
On Jun 19, 2008, at 14:41 , Martijn Faassen wrote:
Tres Seaver wrote:
Christian Theune wrote:
[snip]
My preference would be to have more important changes first.
Please don't make it a judgement call: keep it time-descending
order,
just like the releases. Among other things, this makes
On Jun 18, 2008, at 12:09 , Christian Theune wrote:
- A change on a branch is recorded in the next unreleased section.
(Merges of
the same fix over multiple branches are not recorded in different
places on
the other branches.)
This results in the following properties for the CHANGES.txt:
On Jun 18, 2008, at 14:32 , Christian Theune wrote:
Hi,
On Wed, Jun 18, 2008 at 01:11:46PM +0200, Jens Vagelpohl wrote:
Just for clarification, does this imaginary scenario describe what
you
mean?
- I am fixing a problem in the 1.2-branch of my Foobar product and
note
the fix
On Jun 18, 2008, at 15:07 , Christian Theune wrote:
On Wed, Jun 18, 2008 at 02:48:22PM +0200, Jens Vagelpohl wrote:
So in essence it sounds like changes will be noted in CHANGES.txt for
*all* those branches and the trunk that they're applied to, and the
only
difference is the version
On Jun 18, 2008, at 19:00 , yuppie wrote:
Why do we maintain a CHANGES.txt file? Who reads it and why?
The audience I have in mind are users of released versions. They
read CHANGES.txt to figure out what's new in a release.
Let's take Zope 2 as an example:
Most people will currently use
On Jun 18, 2008, at 19:27 , yuppie wrote:
That's not the only audience. I as a developer consult CHANGES.txt
to (hopefully) find *all* changes on the respective branch or on
the trunk that have flowed into it until now.
Can't developers use the subversion history?
It's much quicker to
On Jun 18, 2008, at 19:32 , Fred Drake wrote:
On Wed, Jun 18, 2008 at 1:27 PM, yuppie [EMAIL PROTECTED]
wrote:
Sorry. I was referring to the current Zope 2 (and CMF) policy:
Note that you don't need to note the fix in the CHANGES.txt on the
trunk if
you don't want to. At the time a new
Hi guys,
Are there any basic problems using z3c.form with Zope 2? All the
tutorials and documentation I have found uses straight Zope 3. If
anyone has successfully used z3c.form in a Zope 2 project I'd love to
see some sample code ;-)
jens
The zope.org-related servers and services maintained by Zope
Corporation will be moving to a new home late Thursday night Eastern
Standard Time.
What services are affected?
---
The most important service addresses include...
- www.zope.org
- svn.zope.org
-
On Jun 11, 2008, at 06:05 , Marius Gedminas wrote:
On Wed, Jun 11, 2008 at 01:22:18AM -0500, Jens Vagelpohl wrote:
The zope.org-related servers and services maintained by Zope
Corporation
will be moving to a new home late Thursday night Eastern Standard
Time.
How long will the outage
On May 28, 2008, at 02:25 , Christian Theune wrote:
On Tue, May 27, 2008 at 02:31:04PM -0400, Jim Fulton wrote:
Did you try setting up a download cache and putting it there? Note
that
if you had a download cache named foo, you would need to put the
tar
ball in foo/dist.
I could and
Hi guys,
Does zc.buildout and/or the default egg recipe have any way of
overriding the download URL from the cheese shop if that URL is broken
and I cannot reach the package maintainer?
Thanks!
jens
___
Zope-Dev maillist - Zope-Dev@zope.org
On May 27, 2008, at 12:49 , Jim Fulton wrote:
On May 27, 2008, at 1:42 PM, Jens Vagelpohl wrote:
Hi guys,
Does zc.buildout and/or the default egg recipe have any way of
overriding the download URL from the cheese shop if that URL is
broken and I cannot reach the package maintainer
On May 27, 2008, at 13:31 , Jim Fulton wrote:
Did you try setting up a download cache and putting it there? Note
that if you had a download cache named foo, you would need to put
the tar ball in foo/dist.
Haven't tried that yet.
jens
___
On Apr 30, 2008, at 12:41 , Christian Theune wrote:
On Wed, Apr 30, 2008 at 12:16:53PM +0200, Wichert Akkerman wrote:
I'm trying to figure out what the current state of the art for
monitoring Zope2 processes is. Ideally I'ld want the equivalent of
zc.z3monitor.
I figured the medua
On Apr 18, 2008, at 14:09 , Stephan Richter wrote:
On Friday 18 April 2008, Wichert Akkerman wrote:
There is still an ongoing debate about that even - the extjs authors
basically only want to offer LGPL to you if you meet certain criteria
but won't allow you to redistribute it with just
On Apr 17, 2008, at 12:27 , Hanno Schlichting wrote:
Opinions, votes?
+1
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
On Apr 14, 2008, at 19:11 , Philipp von Weitershausen wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those
failing Plone tests, merge the branch and be on our way.
+1
jens
___
Zope-Dev maillist - Zope-Dev@zope.org
101 - 200 of 434 matches
Mail list logo
