Gianugo Rabellino wrote:
Torsten Curdt wrote:
Well, actually my point is about user awareness. Today you just
download Cocoon, read the docs, type ./build.sh and see some
fast-scrolling messages muttering about unstable stuff, and that's
it. I'm thinking of something more specific that forces the user to
know what she's doing. A different property/target (./build.sh
-Dinclude.unstable=true)? A different file to edit
(local.unstable.block.properties)? Everything would do: but clearly a
message that scrolls during the build is not enough.
Well, having it disabled by default is a clear sign?
That's not the case for a helluvalot of unstable stuff as of today...
I know ...sorry my answer was misleading...
I like to propose to disable unstable blocks
by default.
cheers
--
Torsten
