Gentlemen,

May I suggest that before you remove that warning,
consider upgrading the documentation just a bit.

I've been struggling for weeks now to implement a
simple rework of the default authoring environment to
use CSS instead of tables, without success.

Whilst it's completely up to you folks, if you have a
bunch of new people using 2.0 without better
documentation, you should expect a flood of email help
requests.

I'm happy to help rewrite parts of the wiki and
documentation, if I can ever figure things out myself
(no easy task if you're new to Lenya)!

Cheers,
    - Steve

--- Jörn Nettingsmeier <[EMAIL PROTECTED]> wrote:

> hi everyone!
> 
> 
> i think it's time we removed the frightening warning
> from the 2.0 
> website ("Apache Lenya 2.0 is still under heavy
> development and should 
> not be used for production yet.")
> 
> i suggest changing the warning to a note such as
> 
> "Apache Lenya 2.0 is steadily approaching release
> candidate status. 
> Don't bet your job on it just yet, but otherwise it
> is already perfectly 
> usable for small-scale and private website
> deployments. If you are 
> considering Lenya 2.0 for something bigger, please
> consult the user 
> mailing list first, describing your needs in some
> detail. We will try to 
> asses whether 2.0 is for you at this point."
> 
> this is just an off-the-cuff draft to get started,
> please suggest 
> improvements.
> 
> wdyt?
> 
> regards,
> 
> jörn
> 
> 
> 
> -- 
> Jörn Nettingsmeier
> 
> Kurt is up in heaven now.
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 



       
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to