On 2/23/06, Peter Simmons <[EMAIL PROTECTED]> wrote:
> of was one of the above people wanted to install a new component to add
> some functionality to their site. e.g. add a shopping cart/checkout
> component . I think it would be great if the site administrator could
> add this component to their
On Wednesday 22 February 2006 10:58, Dominik Huber wrote:
> Do you have an other solutions for this problem?
Honestly, I had not thought about this case, but it is clearly a valid use
case.
What about this structure?
repos/main/
NAMESPACE/
branches/
tags/
trunk/
The Buildbot has detected a failed build of Zope3 branches 3.2 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 3208
Blamelist: benji_york,mgedmin,mj,oestermeier,poster,srichter,whitmo,yuppie
BUILD FAILED: failed failed slave lost
sin
The Buildbot has detected a failed build of Zope3 trunk 2.4 Windows 2000
zc-bbwin3.
Buildbot URL: http://buildbot.zope.org/
Build Reason: The web-page 'force build' button was pressed by 'benji':
restarted bbwin-2 after it went purple
Build Source Stamp: None
Blamelist:
BUILD FAILED: failed
Stephan Richter wrote:
On Wednesday 22 February 2006 10:58, Dominik Huber wrote:
Do you have an other solutions for this problem?
Honestly, I had not thought about this case, but it is clearly a valid use
case.
What about this structure?
repos/main/
NAMESPACE/
branches/
Dominik Huber wrote:
We came up with the same solution first. But our problem appears within
the following use case.
A few developers are sharing code on application level (not package
level!) for different dedicated customer projects. They have problems to
setup identical dev-environments (
Benji York wrote:
Dominik Huber wrote:
We came up with the same solution first. But our problem appears
within the following use case.
A few developers are sharing code on application level (not package
level!) for different dedicated customer projects. They have problems
to setup identical
On Thursday 23 February 2006 20:29, Jim Fulton wrote:
> This is quite a document and vision. I hope we can pull something
> like it off. (Like many, I recognize the daunting size of the task.)
I have already working parsers and writers for all file formats. I have also a
preliminary (but tested