Philipp von Weitershausen wrote:
I personally prefer not working with the tree anymore. If people want
to keep it around, that's fine, but then they should maintain it.
+1
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing
On 5 Jul 2007, at 16:45 , Christian Theune wrote:
Am Donnerstag, den 05.07.2007, 16:32 +0200 schrieb Philipp von
Weitershausen:
Christian Theune wrote:
I've made the release branch for Zope 3.4, you can feel free to
start
introducing changes for Zope 3.5 into the trunk of the tree.
It
Stephan Richter wrote:
On Thursday 05 July 2007 09:27, Benji York wrote:
Christian Theune wrote:
I've made the release branch for Zope 3.4, you can feel free to start
introducing changes for Zope 3.5 into the trunk of the tree.
Now would seem to be the time to discuss the fate of the big
Am Donnerstag, den 05.07.2007, 16:32 +0200 schrieb Philipp von
Weitershausen:
Christian Theune wrote:
I've made the release branch for Zope 3.4, you can feel free to start
introducing changes for Zope 3.5 into the trunk of the tree.
It should be noted that the 'Zope3' tree actually
On Thursday 05 July 2007 10:48, Philipp von Weitershausen wrote:
I'm not sure what the interaction patterns are, e.g. who's responsible
for updating the tree's pointers to newer packages. The maintainers of
those packages? They probably know best ...
I disagree. While Stephan raises a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
On 5 Jul 2007, at 16:45 , Christian Theune wrote:
Am Donnerstag, den 05.07.2007, 16:32 +0200 schrieb Philipp von
Weitershausen:
Christian Theune wrote:
I've made the release branch for Zope 3.4, you can feel free
On 5 Jul 2007, at 17:18 , Stephan Richter wrote:
On Thursday 05 July 2007 10:48, Philipp von Weitershausen wrote:
I'm not sure what the interaction patterns are, e.g. who's
responsible
for updating the tree's pointers to newer packages. The
maintainers of
those packages? They probably know
