Forum .LRN Q&A: Re: .LRN 2.0.1 released
Special thanks to:
Joel who has become one of the OpenACS titans (holding up the community like Atlas with his manic testing episodes, documentation push, and OpenACS release management), Tracy (who at very short notice jumped in and quickly got an overview and helped get .LRN out the door as the release manager), and Andrew who spent at least two weeks on a show stopping bug and upgrade scripts (and also helped us test on the Heidelberg install).
Oh yes, and one other thing: thanks especially for putting up with my (probably) ineffective prodding per email and IM.
Dirk Gomez identified and is fixing several critical bugs in .LRN 2.0.1:
- #1569. Review item_type subquery on weeks view
- #1567. Files cannot be properly accessed in file-storage portlet
- #1511. Cannot access files in default folders
- Also, these bugs, most of which were fixed a long time ago, are still not closed. It would be great if some testers could verify them. So if the two German translations get completed rapidly, and the bugs are fixed, we can either release .LRN 2.0.2 this week or decide that some of the priority 2 bugs also need to get fixed, identify people to fix them, and set a target date.
Here's the diff: http://xarg.net/tools/cvs/change-set-details?key=98707BF70F8A79A17B8BEE1745BBF0FDAA99896F
The pages now all work, but the code was suspicious and so were my changes.
There is an i18n issue left which isn't easy at all to be fixed: namely that folder names can be localized. You have #fs-portlet.Projects# as a folder name and "Dirk's Secret MP3 Archive" which apparently isn't supposed to be translated into any other language.
I don't know if there is a quick fix. I think a proper fix would be a presentation column (a little bit along the lines what Branimir suggested a couple of weeks ago)
This column would hold a tcl proc that is applied automagically to the corresponding content and thus would magically localize #fs-portlet.Projects#.
In light of our discussion as managing .LRN as a vertical application (or whatever name we choose) of OpenACS, I'd suggest that the question of "when is a given package a package" should be considered in the OpenACS community. .LRN is obviously interested, but we want to manage things in a clear way. Would you be willing to bring the issue to that forum?