On 20 Dec 2005, at 19:47, Andreas Jung wrote:
--On 20. Dezember 2005 14:27:18 -0500 Paul Winkler
[EMAIL PROTECTED] wrote:
just to be clear, the stuff I'm talking about is ZMI user interface
docs, not programmer docs.
I'll raise the question again: what are the benefits of the HelpSys
that may be confounding our efforts to
run windows tests with buildbot.
Jim
Jens Vagelpohl wrote:
On 19 Dec 2005, at 22:08, Jim Fulton wrote:
Sounds good. I'll announce that the repo will be down for
maintenance
on the 25th,
Just FYI, during a dry run this morning I hit an obvious snag
On 21 Dec 2005, at 16:12, Jim Fulton wrote:
Jim Fulton wrote:
I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.
Done
Great. I can see http://svn.zope.org works just fine.
With
On 21 Dec 2005, at 18:47, Jim Fulton wrote:
I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work. Question is, is it worth
delaying the release? I don't know.
IMHO it is an
On 21 Dec 2005, at 16:15, Jens Vagelpohl wrote:
With this upgrade in place I will do a new dry-run for the FSFS
backend migration tomorrow morning.
The test run ran through without any problems. Here's some stats:
- dumping the existing repository took 12 minutes and resulted in a
1.1 GB
On 23 Dec 2005, at 14:48, Jim Fulton wrote:
Jim, if you want to take a look at this new repository, it's
under / root/fakesvn.
I moved this to the normal repos area and changed the group to
the zopesvn, so that everyone with access to the old repository
should have access to this one. The
On 23 Dec 2005, at 14:57, Jens Vagelpohl wrote:
On 23 Dec 2005, at 14:48, Jim Fulton wrote:
Jim, if you want to take a look at this new repository, it's
under / root/fakesvn.
I moved this to the normal repos area and changed the group to
the zopesvn, so that everyone with access
Hi all,
Just got finished migrating the main repository on svn.zope.org away
from the old BDB backend to a FSFS backend. Some quick tests show me
that everything seems to be in order, including sending of commit
messages.
This means the repository is open for business again.
jens
On 15 Feb 2006, at 15:30, Philipp von Weitershausen wrote:
* I plan on doing the migration some time during the PyCON
conference or
sprint (24 Feb through 2 Mar). There might be a period of 1 day or so
when commits to Five won't be possible. I'll inform everyone in
advance.
Perhaps Jens
On 18 Feb 2006, at 13:08, Stephan Richter wrote:
On Friday 17 February 2006 23:54, Jim Fulton wrote:
Only you and Philipp were excited about this. Not sure that
constitutes a ringing endorsement. Maybe others will chime in now.
I'm +10 too.
I'd like to see this happen before the end of
On 13 Mar 2006, at 15:15, Andreas Jung wrote:
Due to some changes in my email configuration I would like to use
another email address for checkin notifications email other than the
current one. Is there a way to configure this on my own or do I
have to
beg before the svn admistrator?
The
I've set up a new mailing list that gets all checkins for the
zope.org CVS and Subversion repositories:
http://mail.zope.org/mailman/listinfo/checkins
Does this list replace [EMAIL PROTECTED] as the default checkins list?
jens
___
Zope-Dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:07, Jim Fulton wrote:
I think the XML export is a facility that is and should be advertized
as a legitimate escape hatch for data kept in Zope. People really
shouldn't feel afraid of putting data in Zope/ZODB as there
really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:12, Jim Fulton wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:07, Jim Fulton wrote:
I think the XML export is a facility that is and should be
advertized
as a legitimate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:25, Jim Fulton wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more clearly document their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:30, Jim Fulton wrote:
Interesting. I imagine that this is fixible in a somewhat
straightforward
way, although it is probably tied up with the general encoding
mess in Z2.
Yes, that's likely where the problem comes from.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27 Mar 2006, at 11:55, Philipp von Weitershausen wrote:
Andreas Jung wrote:
Zope 2.8 ships/shipped with Five 1.0 which is very old and no longer
actively maintained. Most ppl doing currently development with Zope
2.8 are using Five 1.2. Should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17 Apr 2006, at 14:15, Andreas Jung wrote:
Hi,
almost all big Zope projects have changed to Subversion
fortunately. Using
svn:externals is a nice way to build bundles and helps a lot
deploying software. However projects still have some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18 Apr 2006, at 08:30, Andreas Jung wrote:
--On 17. April 2006 16:25:10 +0200 Jens Vagelpohl
[EMAIL PROTECTED] wrote:
Wouldn't it make sense to migrate the complete Products hierarchy
from cvs.zope.org to svn.zope.org?
- -1 on migrating
+0200, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18 Apr 2006, at 08:30, Andreas Jung wrote:
--On 17. April 2006 16:25:10 +0200 Jens Vagelpohl
[EMAIL PROTECTED] wrote:
Wouldn't it make sense to migrate the complete Products hierarchy
from cvs.zope.org
that Basket should really just die in favor of something
going in to Zope 2 proper.
- C
On Apr 22, 2006, at 1:02 PM, Rocky Burt wrote:
Will do.
- Rocky
On Thu, 2006-20-04 at 21:12 +0100, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rocky, since this whole issue seems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23 Apr 2006, at 18:47, Rocky Burt wrote:
On Sun, 2006-23-04 at 19:30 +0200, Florent Guillaume wrote:
Cool. What's the status of it regarding integration directly into
Zope 2.10?
Well, pythonproducts patches regular Zope and also CMF. Five
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23 Apr 2006, at 19:33, Rocky Burt wrote:
Great news regarding CMF 2.1 and Plone. Specifically all
pythonproducts
does for CMF is patch
CMFCore.TypesTool.TypesTool.listDefaultTypeInformation so that when it
looks up a product it doesn't simply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Apr 2006, at 10:59, Lennart Regebro wrote:
I find all these errors that Zope can't find a favicon.ico pretty
annoying. Can we put one into 2.10s root by default, or is that for
some reason a bad idea?
+1 from me. The circle-Z should make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Apr 2006, at 11:43, Philipp von Weitershausen wrote:
Lennart Regebro wrote:
I find all these errors that Zope can't find a favicon.ico pretty
annoying. Can we put one into 2.10s root by default, or is that for
some reason a bad idea?
+1
On 24 Apr 2006, at 11:57, kit BLAKE wrote:
2006/4/24, Jens Vagelpohl [EMAIL PROTECTED]:
Yeah, that's nice. Does it work as a PNG, though? I was under the
impression (and thought the spec requires) that favicons must be
*.ico files.
A PNG favicon will work in the Mozilla family
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just FYI, since the product seems mostly orphaned I just moved it
without asking anyone:
http://svn.zope.org/Products.QueueCatalog
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31 May 2006, at 14:55, Sidnei da Silva wrote:
On Wed, May 31, 2006 at 09:49:49AM -0400, Chris McDonough wrote:
| I've done this (at least with FileStorage) and it's
| sllo. Might be OK for low-traffic sites, but better
| to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3 Jun 2006, at 20:53, Florent Guillaume wrote:
On 3 Jun 2006, at 20:46, Jens Vagelpohl wrote:
On 3 Jun 2006, at 18:49, Florent Guillaume wrote:
I didn't see the GenericSetup checkin creating that tag, could
you check that you're subscribed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14 Jun 2006, at 09:44, Andreas Jung wrote:
--On 14. Juni 2006 07:32:42 +0100 Chris Withers
[EMAIL PROTECTED] wrote:
I know the good reasoning behind the time-based releases, but have
they
really worked out?
Yes and No.
Yes: It's a must
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16 Jun 2006, at 10:28, Andreas Jung wrote:
My recommendation:
1 yr deprecation period as it is now
1 yr + X maintenance period for older branches.
+1
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Jun 2006, at 15:51, Chris Withers wrote:
Florent Guillaume wrote:
Hopefully the google archive trail will be enough for this issue...
When I look for bugs to fix I don't read the mailing list archives
for the past two years, I use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Jun 2006, at 16:35, Tres Seaver wrote:
I believe that the extra flexibility which zpkg is intended to provide
(dependency-based subset distributions, primarily) would be better
served by moving Zope to use eggs, and that we should thus retire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30 Jun 2006, at 14:30, Julien Anguenot wrote:
For maximum reliability I tend to forego the built-in log
reopening in
favor of using the logrotate utility in copytruncate mode. This
will
not require any log file reopening, logrotate will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17 Jul 2006, at 12:24, Andreas Jung wrote:
What about loading FS ZPT's and things like CMF's FSZPT?
Ask Tres or Jens :-)
CMFCore/FSPageTemplate does not do anything special, it defers to the
PageTemplate implementation.
jens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Aug 2006, at 19:19, Andreas Jung wrote:
Some time ago the following patch was proposed to control the timing
for opening the socket ports upon startup:
http://mail.zope.org/pipermail/zope-dev/2005-November/025709.html
I propose to adapt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Aug 2006, at 22:33, Dennis Allison wrote:
Have you compressed the Data.fs? There is an option in the control
panel
to do this. I can be run on a live machine, but you may not want
to do so
given the size of stuff. I'd do it on a quiet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30 Aug 2006, at 14:32, Christian Theune wrote:
Chris Withers wrote:
Christian Theune wrote:
b) it's more convenient for developers
Why?
Early open port means: zopectl restart and reload in your browser
immediately without getting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Sep 2006, at 13:19, Andreas Jung wrote:
Another point with this whole half-yr release cycle: we're going to
confuse
more and more professional users about which Zope version to use
for what.
I've heard from my major customer but also from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Sep 2006, at 14:44, Martijn Faassen wrote:
Another point with this whole half-yr release cycle: we're going
to confuse
more and more professional users about which Zope version to use
for what.
I've heard from my major customer but also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 Oct 2006, at 17:38, Wichert Akkerman wrote:
I noticed that ZopeVersionControl is still actively maintained in CVS.
Would its maintainers mind moving it to subversion? That would make
it a lot easier for us to include it in the Plone 3.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 Oct 2006, at 18:55, Jens Vagelpohl wrote:
On 6 Oct 2006, at 17:38, Wichert Akkerman wrote:
I noticed that ZopeVersionControl is still actively maintained in
CVS.
Would its maintainers mind moving it to subversion? That would make
it a lot
On 12 Oct 2006, at 09:32, Wichert Akkerman wrote:
I did a bit of checking: zope.org has a crazy number of DNS servers
and they are not all in sync. Particularly
seconly.rackspace.com (69.20.0.180) and cabana.palladion.com
(64.34.177.88) are not authorative for the zope.org domain and will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Oct 2006, at 09:36, Justizin wrote:
That record comes from zoneedit.com, noone should be using those
servers for lookups AFAIK because zoneedit.com is not authoritative
for the NS records.
These are slaves which have not coordinated with me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Dec 2006, at 03:44, Rob Miller wrote:
is there a current maintainer or development process for
ZopeVersionControl? there's been a little bit of activity lately,
but it's still in CVS.
in any event, CMFEditions (a versioning system for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23 Dec 2006, at 14:23, Jim Fulton wrote:
zdaemon is an interesting case because it is s non-zope and
(mostly) non-python specific. I must say that it amazes me that there
isn't an established alternative out there.
When people start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23 Dec 2006, at 14:53, Jim Fulton wrote:
I don't think it ever caused anyone any headache apart from maybe
working
around different ways in which forking/daemonizing is handled on
some platforms (OS X comes to mind).
Any software we own is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14 Jan 2007, at 11:26, Andreas Jung wrote:
Running the ZPublisher tests (on the trunk) alone results in the
following error. However the tests works when running all
unittests. Bug or feature?
If a test runs one way and not another there's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Feb 2007, at 22:36, Dieter Maurer wrote:
* my code uses 2 blank indentation rather than the usual 4 blank
(to make it more readable and easier to maintain for me)
That can be dealt with by reformatting. Should not be hard to quickly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 Feb 2007, at 12:47, Wichert Akkerman wrote:
I'm not quite sure it has to be part of Zope 2 as you install it.
Having
it in svn.zope.org would go a long, way, though, allowing us to use
svn:externals during development and potentially fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 Feb 2007, at 18:27, Philipp von Weitershausen wrote:
Note that we have the same issue with ZopeVersionControl, which is
currently only in CVS. An import of that into subversion would
make a
lot of us very happy.
I think it has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: UNKNOWN : CMF-2.1 Zope-trunk Python-2.4.4 : Linux
From: CMF Unit Tests
Date: Sun Mar 11 22:42:15 EDT 2007
URL: http://mail.zope.org/pipermail/cmf-tests/2007-March/004319.html
Subject: UNKNOWN : CMF-trunk Zope-trunk Python-2.4.4 : Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12 Apr 2007, at 13:35, Miles wrote:
However, having logged this, the testrunner proceeded to run all my
tests correctly, and so the buildbot reported a pass. I expected
the testrunner to bomb out on encountering this error, but it
didn't -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Apr 2007, at 19:28, Christopher Lozinski wrote:
On his personal home page http://zwiki.org/JimFulton Jim Fulton,
the Zope Pope writes:
Make ZWiki subclassable from ZClasses. This will make it a lot
easier to experiment and innovate.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Aug 2007, at 08:04, Andreas Jung wrote:
to make it short: I propose to move the Zope 2 bugtracker to
Launchpad. Since the Zope 3 bugtracker works already with success
on LP
we should follow with the Zope 2 bugtracker. Objections?
One
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Aug 2007, at 09:11, Andreas Jung wrote:
Slow down... speaking for the CMF and PAS collectors:
I'm -0.5 on both since I actively use them and I have no
experience at
all with Launchpad. The other responsible people sit on the CMF
list so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Aug 2007, at 11:11, Hanno Schlichting wrote:
One could also move the CMF bugtracker to LP at the same time.
Then only
the APE and the PAS trackers would remain. The PAS tracker is already
empty and the APE tracker is also pretty much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Aug 2007, at 11:26, Hanno Schlichting wrote:
Jens Vagelpohl wrote:
On 13 Aug 2007, at 11:11, Hanno Schlichting wrote:
One could also move the CMF bugtracker to LP at the same time.
Then only
the APE and the PAS trackers would remain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 Oct 2007, at 15:57, Jim Fulton wrote:
Any objections?
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
Good idea. +1 from me. I'm not on zope3-dev but won't mind additional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 Oct 2007, at 17:20, Andreas Jung wrote:
The distinction between Zope 2 and Zope 3 must disappear. We must
speak of Zope. Everything else is counterproductive when it comes
to promoting Zope. There is only one Zope developer community and
On Nov 16, 2007, at 10:36 , Chris Withers wrote:
Tres Seaver wrote:
How do you go about mapping from old collector issue numbers to
new launchpad ticket numbers?
You let the www.zope.org redirect you.
Well, I'm not sure it does...
I'm looking at a changelog and it has a specific old
On Feb 22, 2008, at 17:52 , Andreas Jung wrote:
Hi,
I (and some co-workers) encountered lately issues with traversal
when running scripts using zopectl run from the command line. The
lookup
code fore views apparently expects always the existence of a REQUEST.
What's the best approach to
On Mar 10, 2008, at 17:57 , Wichert Akkerman wrote:
Previously Tres Seaver wrote:
Gary Poster wrote:
Also, some variety of doctest would be nice. Even when a package is
not using doctests, I add new tests as doctest unless there's a
really
good reason not to.
Becuase they make for poor
On Mar 26, 2008, at 01:12 , Timothy Selivanow wrote:
I would rather have a package that upstream approves of and
participates
in, than blindly create it in a silo not caring. It never turns out
well in the long run with the latter.
You may be fighting windmills here. Previous attempts at
On Apr 5, 2008, at 17:52 , Martin Aspeli wrote:
Then, we need a champion for each of the sub-projects. These are:
- Zope 3 and the Zope Libraries -- this is the most important one
in
the short term!
- Zope 2
- CMF
- ZODB
I'm volunteering for the CMF.
jens
On Apr 7, 2008, at 00:20 , Alexander Limi wrote:
- Try not to be too clever with the Taste/Get and other links.
People actually scan for links that are similar from other projects,
and having to interpret/understand them is confusing.
+1
- The list of companies using Zope includes
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
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 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 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
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 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
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
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
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
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 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 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 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 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 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
-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
-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 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 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 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
701 - 800 of 1121 matches
Mail list logo
