Hello Stephan,
Simple, effective, great. Thanks.
Monday, September 11, 2006, 7:45:42 PM, you wrote:
On Monday 11 September 2006 13:23, Adam Groszer wrote:
The solution might be simple, but at this late time I don't see it.
Any help is welcome.
No, the solution was not even possible
Over the last couple of days we've been discussing Zope's new release
cycle and the release management. I would like to sum up what seems to
be the gist of those discussions:
9 month release period?
---
Several consumers of Zope releases have talked about their experience
Hey,
Philipp von Weitershausen wrote:
[snip]
Thoughts?
I don't have time for a discussion right now as I'm off to Germany soon.
The one thought that strikes me is that these release management notes,
when finalized, should be in some clear, findable, well-known and
maintained location.
Martijn Faassen wrote:
I don't have time for a discussion right now as I'm off to Germany soon.
The one thought that strikes me is that these release management notes,
when finalized, should be in some clear, findable, well-known and
maintained location. Otherwise we'll forget again. I know,
Philipp von Weitershausen wrote:
Shall we release once every 9 months from now on?
9 months pregnancy -- that's almost poetic.
/Anton
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub:
Previously Anton Stonor wrote:
Philipp von Weitershausen wrote:
Shall we release once every 9 months from now on?
9 months pregnancy -- that's almost poetic.
And painful to deliver?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/
Hi everyone,
I just noticed that zope.conf.in has now the following entry:
zodb
demostorage
zeoclient
server localhost:8100
storage 1
cache-size 20MB
/zeoclient
/demostorage
/zodb
This means that ZEO has to start up to run Zope after a default check
out/download. When I had no
Stephan Richter wrote:
Hi everyone,
I just noticed that zope.conf.in has now the following entry:
zodb
demostorage
zeoclient
server localhost:8100
storage 1
cache-size 20MB
/zeoclient
/demostorage
/zodb
This means that ZEO has to start up to run Zope after a default check
On Wednesday 13 September 2006 11:02, Florent Xicluna wrote:
Currently, I work with 3.3 branch for my company. I checked out the trunk
too, in order to collaborate to Zope development.
So I have both '/trunk' and '/branches/3.3/' on my computer. When I prepare
a fix I do it on the 3.3 branch,
On Sep 13, 2006, at 11:23 AM, Stephan Richter wrote:
On Wednesday 13 September 2006 11:02, Florent Xicluna wrote:
Currently, I work with 3.3 branch for my company. I checked out
the trunk
too, in order to collaborate to Zope development.
So I have both '/trunk' and '/branches/3.3/' on my
On 9/12/06, Jim Fulton [EMAIL PROTECTED] wrote:
FWIW, I use the following approach:
- Early in the process, I mark every real reproducable bug as blocking.
In this last go around, this included a number of bugs that had been
around for months or years.
- Later in the process I downgraded
Florent Xicluna wrote:
However i have a worry on the Fix oldest branch, merge to newer branches.
I guess this is due to my young experience with SVN development.
Currently, I work with 3.3 branch for my company. I checked out the trunk too,
in order to collaborate to Zope development.
So I have
Stephan Richter wrote:
On Wednesday 13 September 2006 11:02, Florent Xicluna wrote:
Currently, I work with 3.3 branch for my company. I checked out the trunk
too, in order to collaborate to Zope development.
So I have both '/trunk' and '/branches/3.3/' on my computer. When I prepare
a fix I do
Philipp von Weitershausen wrote at 2006-9-13 11:05 +0200:
Over the last couple of days we've been discussing Zope's new release
cycle and the release management. I would like to sum up what seems to
be the gist of those discussions:
9 month release period?
---
I am almost
14 matches
Mail list logo
