Gregor J. Rothfuss wrote:
Andreas Hartmann wrote:
We once agreed to avoid backwards-incompatible changes in stable
branches, i.e., when 1.4 is released there may not be any backwards-
incompatible changes anymore. We would have to setup a new trunk
(1.6-dev), and this would mean to maintain 3 branches. IIRC the
community
agreed that this is too complex.
I'm totally in favor of the "release early, release often" credo,
but I can't see how we could manage it ... How do other projects
with small communities handle this situation?
at the time of 1.4 branching, we would stop maintaining the 1.2 branch.
why? If there are people using 1.2 and if there are core developers willing
to further patch 1.2, then I don't see any reason to declare it
unmaintained.
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
