Thorsten Scherler wrote:
I think we should talk about blockers,
I think the UUID problem is a blocker ;-)
resolve them and do a 1.4.1
release. I hope that many committer will review the 1.3 revolution and
then we should start a 1.5 branch where we take the best from 1.3 and
1.4 and add all new features that are still missing 1.4.
1.4 is way too long in development then to have radical changes since
this means all 1.4.
it's not a radical change, but rather finish something which we have
started and prepared quite some
time ago
projects that are already in production would have
to be ported.
better now, than later
Michi
salu2
-- Andreas
If that can not be granted i will vote for
option 2.
2) We should introduce UUIDs in a straightforward manner:
- sitetree references documents using UUIDs
- the persistence layer knows only about UUIDs
- the default persistence impl. uses UUID+language as filename
- links are resolved when a page is rendered
3) The concept of paths should be kept. URLs are mapped to paths,
i.e. the sitetree contains path references. The URL space
might change, the path space might not (otherwise we would
still be moving documents around, which is IMO a bad thing).
4) It should be in 1.4, but I don't like options (2) and (3).
IMO it should be implemented like this:
...
----
Another issue: UUIDs vs. UNIDs
Do you prefer
a) UUIDs (http://en.wikipedia.org/wiki/UUID)
+1
b) Lenya-specific UNIDs which might be human-readable
Jann
--
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]
