hi solprovider!
[EMAIL PROTECTED] wrote:
On 8/9/06, Joern Nettingsmeier <[EMAIL PROTECTED]> wrote:
Joern,
I believe you will be very happy with Lenya 1.3. 1.3 removes Areas;
it uses that portion of the URL for the module. 1.3 adds Revisions,
which make publishing and rollback incredibly easy. 1.3's content
structure is based on UNIDs (or UUIDs), and uses Structures to
maintain hierarchies. Today, you can see how content works with File
and Link resources. Editing XML resources will be added soon; the
code is half written, but I was unable to work on it for the last two
weeks. I am uncertain there will be an upgrade path from 1.4 to 1.3;
content should be easy, but Modules have very different internals.
Hopefully we can merge 1.4's ability to have Module-specific Java
class files if that feature proves useful.
it sure sounds interesting, and my remark about areas did in fact
originate with you earlier comments on that topic.
but i have bet on 1.4 with my project, and there is no chance of me
trying 1.3 unless the day gets significantly longer than 30 hours...
i've worked hard at gaining a little insight into the workings of trunk,
and i'm not in a position to write that off and learn something new atm,
as much as i would like to play with your ideas.
i think the revolution branch is a good idea in itself to see new ideas
come up, and i wish more people would review and collaborate on it, but
at the same time the lenya community is very small and all eyeballs on
the revolution branch are lost for the trunk.... hopefully the 1.3
branch will be used enough that the good concepts in it will be fed back
into the trunk.
1.3 is a symptom of sitting on code too long (both on your part for the
perceived lack of interest of the lenya committers, and on the part of
the committers for maybe having too ambitious or unclear goals).
it's good that the block is now overcome, and for that the 1.3 branch
was certainly necessary.
one might also argue that trunk carries too much cruft, and that a
clean-room rewrite (a "revolution") could do good. 2 months ago, i would
have supported that view.
but lately the committers (notably andreas) have done an amazing
clean-up job, which shows that the evolutionary approach seems to work
very well.
personally (without having looked at 1.3 in depth) i hope that the two
branches will be reconciled in the beginning of the 1.5 period, and that
all developers will be working on the same trunk again. branching should
happen frequently, but only on sub-systems if possible, to ease merging
afterwards.
imho we can afford neither duplicate nor disregarded work in such a
small community, so i do hope that the 1.5 cycle will start with a merge.
best,
jörn
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
