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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
