Max M wrote:
Well, the sooner better...
...this comes mainly from my desire to see the "exponential
combination of branches" problem go away...
Technically speaking, isn't that a squared problem?
That depends how many pieces of software are involved ;-)
Chris
--
Simplistix - Content Manag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> On 6/26/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
>> - -1. The externals are just that, external to the Zope project.
>
> Uhm. I have a hard time seeing Five and lib/python/zope as "external to
> Zope".
They are managed as
On 6/26/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
- -1. The externals are just that, external to the Zope project.
Uhm. I have a hard time seeing Five and lib/python/zope as "external to Zope".
When we get to an egg-based Zope install, I think such a gesture would
map onto "check out the so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> A small question/idea.
>
> When making svn:externals in Nuxeo, we always use https. That way
> trees can still be checked out anonymously, but still modified.
>
> in Zope, threes are checked out with svn+ssh, but externals us
Chris Withers wrote:
Philipp von Weitershausen wrote:
Jim suggested a different strategy with "Zope 5"
(http://mail.zope.org/pipermail/zope3-dev/2006-February/018415.html).
The little bits and pieces that make up Zope 3 (the zope.* packages)
would be developed more or less independently of Zope-
A small question/idea.
When making svn:externals in Nuxeo, we always use https. That way
trees can still be checked out anonymously, but still modified.
in Zope, threes are checked out with svn+ssh, but externals use svn.
That means that when you want to modify for example Five, you need to
dele
Philipp von Weitershausen wrote:
Jim suggested a different strategy with "Zope 5"
(http://mail.zope.org/pipermail/zope3-dev/2006-February/018415.html).
The little bits and pieces that make up Zope 3 (the zope.* packages)
would be developed more or less independently of Zope-the-app-server
(which
Chris Withers wrote:
> Philipp von Weitershausen wrote:
>>
>> Follow this thread:
>> http://mail.zope.org/pipermail/zope3-dev/2005-November/016561.html
>
> *grunt* *sigh*
>
> It has to happen at some stage, surely?
Jim suggested a different strategy with "Zope 5"
(http://mail.zope.org/pipermail/
Philipp von Weitershausen wrote:
Follow this thread:
http://mail.zope.org/pipermail/zope3-dev/2005-November/016561.html
*grunt* *sigh*
It has to happen at some stage, surely?
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Chris Withers wrote:
> Benji York wrote:
>> Philipp von Weitershausen wrote:
>>> Uh, never mind.
>>
>> +1 :)
>
> Any chance you could explain why you feel that way?
Follow this thread:
http://mail.zope.org/pipermail/zope3-dev/2005-November/016561.html
Philipp
__
Benji York wrote:
Philipp von Weitershausen wrote:
Uh, never mind.
+1 :)
Any chance you could explain why you feel that way?
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope3-d
Philipp von Weitershausen wrote:
Uh, never mind.
+1 :)
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Chris Withers wrote:
> Philipp von Weitershausen wrote:
>> Note that this should also extend to the Zope 3 releases. Zope 3.2 is
>> part of Zope 2.9 and will hence be used for quite some time. Yet,
>> bugfixes aren't even backported to the Zope 3.2 branch anymore...
>
> It's this sort of thing tha
13 matches
Mail list logo
