Forum .LRN Q&A: .LRN Release Status Report
2) I'm going on vacation from July 15 to 25.
3) As soon as I'm back, I'll get an .LRN 2.1.2 beta out asap
4) The steps after that depend on exactly what must be in the next release, which I'm still not clear on aside from the ongoing theming work.
5) I'd like to propose have big status meetings on IRC every week, inviting people from all of the different active institutions, a few of which I've heard from directly and others some of you have been contacting. At a minimum, we can ask people to manually test the new beta, including upgrading.
How about Tuesday, July 26, 2005 at 21:00:00 UTC?
This translates to:
2:00 PM in L.A.
5:00 PM in Boston
11:00 PM in Berlin
7:00 AM (Wed) in Sydney
The proposed time isn't great for me, but I should be able to make it some of the time.
As a begining of having the next dotlrn release, i realeased all the packages included in the last stable version of dotlrn (excluding the core packages). Some of them have changed ( take a look at the ChangeLogs https://openacs.org/storage/download/?file%5fid=301731 ).
This is the list of packages that had been released: https://openacs.org/storage/download/?file%5fid=306712
This releases were made about 1 or 2 days before the oacs cvs server went down.
Some of them have changed ( take a look at the ChangeLogs https://openacs.org/storage/download/?file%5fid=301731 ).
The file including the ChangeLogs, reports the changes for the core packages too; but i didnot released them.
Is there a tar ball for this release?
but its not that hard to create one, i guess.
Just export the core packages using the oacs-5-1-compat tag; then go to the packages directory and export all the packages under the module dotlrn-all using the oacs-5-1-compat tag.