I apologize. I was confused. I also was offline since my response to Gregor (shutdown to watch the lightning outside my window), so I did not see the many posts my confusion generated.
To summarize: 1) Lenya 1.2.3 is stable. Several of the issues mentioned were about other releases including 1.4. (Reading the MLs can be confusing; today someone complained on the User ML about the latest development build, and few mention exactly what release they use. Or maybe I have spent too much time creating an Apache chroot with a different libc and fried my brain.) 2) The search issue was originally handled by suggesting downloading source, but the Windows Installer has been fixed so the issue will not recur. (So something good resulted from my confusion.) 3) "Lenya's target audience should know what a gz archive and a MD5 sum is" I disagree. I deal with many large companies. The "Windows programmers" do not know what is a BAT file. They were amazed when I replaced 200 lines of VB causing trouble with a 2-line batch file. Lenya's target audience is anybody who needs a CMS. Understanding enough HTML and XSL to copy/paste into page2xhtml.xsl and page2xhtml-homepage.xsl to make a usable and customized website can help, but is not required. Knowledge of *nix, Java, and anything else should not be expected at all. I need a CMS. Lenya? Download. Run installer. Open program. Type URL into browser and start using. Cool. Tell my colleagues the URL so they can use too. Then (much?) later someone wonders if they can change the design with the company name and colors. But the above scenario must be as easy as possible, so: 4) I still think there should be a large one-click "Download Lenya for Windows" on the homepage. See http://www.mozilla.org/ for an example. Another site (I forgot which) has an even bigger "Windows Download Here" with a much smaller "other downloads" below it. (I just added this to Bugzilla. Does it belong there?) 5) Upgrading causes headaches. This is difficult for all software. Some companies/projects just announce old implementations will not work with the latest release; those companies tend to disappear. My company details how each code change will affect the previous release, and if so, requires the patch to fix the upgrade process too. We do require upgrades to every release; each upgrade only handles the last release; but we release seldom enough (and the upgrades are free) so all of our customers have upgraded before the next release. Lenya is more complicated because of parallel development. Will everybody need to upgrade 1.2.2 to 1.2.3 to 1.2.4 to be able to upgrade to 1.4? This could be required if upgrades were easy, but the 1.2.2 to 1.2.3 upgrade issues will hurt. Lenya1.4 needs upgrade code for each 1.2 release starting with 1.2.2. There will be milestone releases where all the upgrade code is discarded. Our process loops through each document, and calls the appropriate upgrade function. The functions only deal with one type of document. Lenya should have an upgrade process for XSL, XSP, JS, XMAP, IML and GML, various XCONF, siteree.xml, content XML, Flow Form XML, and more. Each file should be considered as a data during upgrade. Some is easy. Modifications outside a publication should be discarded; anyone who customizes the main program must remember their changes, except maybe the publication "upgrade XSL" could be applied to the global XSL (for "login" and "choose publication") XSL if those documents have not changed much. Creating a framework for this is a chore, but it should only need to done once. Hopefully Lenya can implement something similar, and figure out how to make it mandatory for each patch to keep it current. Sorry, solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
