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.
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.
The major problem of Lenya 1.4 is that Lenya forces you to accept a specific
data structure which doesn't make sense, because it's a lock-in and totally
unecessary, because if one separates the navigation properly from the
data storage
with a good data abstraction layer in between, then it's no problem at all.
When I started Lenya some years ago that was one of my major goals and I
still think it's one of the most important things re content management,
because it means
one can share information with other applications, build on content
repositories of
other applications (e.g. DSpace) and no content migration is necessary
anymore.
This means you don't have to worry about backwards compatibility anymore
re content.
Re the rest of Lenya I can tell you one thing for sure: There will
always be changes. So one has to think how to live with that without
breaking backwards compatibility. There are several ways to deal with
this, e.g.
- deprecation (instead just removing stuff)
- delegation
- discussing/announcing changes before actually doing them
- madatory migration tools in the case of breaking backwards compatibility.
Unfortunately I don't see this happening currently within this community and
the reason I think this is not happening is because some of the core
developers
are either not using Lenya in production or are considering it as their
private toy.
This might sound harsh, but I cannot explain it otherwise that so little
respect is being shown re people who actually use Lenya and I believe
that this behaviour is
destroying the user base completely.
On the other hand I have to admit that I don't understand why not more
users complain about this big time. Either there are none, or they don't
dare to complain, or they have infinite resources to keep running behind
changes or whatever.
Michi
Angelo.
Modena - Italy
---------------------------------------------------------------------
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]
