Andreas Jung wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk should only be
used for bugfixes *only* until the branch is cut. So no new development
and feature should happen on the trunk until then..Use your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Andreas Jung wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk should only be
used for bugfixes *only* until the branch is cut. So
Hi!
Tres Seaver wrote:
Philipp von Weitershausen wrote:
Andreas Jung wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk should only be
used for bugfixes *only* until the branch is cut. So no new development
Hi!
Andreas Jung wrote:
--On 30. Mai 2006 10:17:08 +0200 Andreas Jung [EMAIL PROTECTED] wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk should only be
used for bugfixes *only* until the branch is cut. So
--On 30. Mai 2006 19:25:06 +0200 yuppie [EMAIL PROTECTED] wrote:
Hi!
Andreas Jung wrote:
--On 30. Mai 2006 10:17:08 +0200 Andreas Jung [EMAIL PROTECTED] wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Hi!
Andreas Jung wrote:
--On 30. Mai 2006 10:17:08 +0200 Andreas Jung [EMAIL PROTECTED] wrote:
I plan to create a branch for Zope 2.10 after 2.10beta 2 or short before
the 2.10 final release. This means that the Zope trunk
Tres Seaver wrote:
yuppie wrote:
Who made up that policy? And why?
I don't think it's a good policy. It is very unlikely that people want
to mess up the trunk right after the first beta. I'd prefer a policy
like that::
After the first beta of the new feature release is made, we
create a
--On 30. Mai 2006 20:09:27 +0200 yuppie [EMAIL PROTECTED] wrote:
You are arguing against a feature freeze policy for the trunk and I agree
with you.
But that is not what I propose. Often people don't *want* to check in new
features for quite a while after the beta. And in that case I see the
