Angelo Turetta wrote:
Andreas Hartmann wrote:
Andreas proposed to remove the source extension, and there was not much
feedback from the community. In a case like that it seems ok to me for a
developer to go ahead and implement a proposed change.
I agree to that (in trunk) - what do the others think?
Do we want to require a specific announcement mail before changes
which require adapting existing content or code, with a certain
period of delay so that others can state their objections?
my €0.02
The real problem is another.
HEAD is so different from (and better than) 1.2x that many people have
begun using it in production. This make the user wish that /trunk be put
in a 'feature freeze' mode, which is incompatible with development.
Yes, I agree that this is a major problem.
The solution is: release often. Better to freeze a version not perfect
than keeping the HEAD codebase a moving target which users won't be able
to build upon. Once you release every, say, 6 months, you'll be free to
make backward incompatible changes in trunk.
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?
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
