.LRN 2.5 Release Management

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 06 Nov 2016, at 10:02 AM

About

• Next stable release: 2.5.0
• Las stable release: 2.4.1
• Tentavive deadlines:
  • may 31, 2009: code freeze and branch
  • june 1, 2009: alpha release process starts
  • june 15, 2009: beta release
  • july 15, 2009: final release

.LRN 2.5 will contain the packages included in the following cvs modules:

• acs-core
• dotlrn-all
• dotlrn-extras

See Aliases at CVS for a detailed list of the packages included in those modules.

Releases are coordinated by the .LRN Leadership Team.

Weekly technical meetings in IRC at openacs channel:

• Summer: Wednesdays, following the OCT one at 16:00 GMT
• Winter: Wednesdays, following the OCT one at 17:00 GMT.

To-do List

• Databases support:
  • Postgresql 8.2 and 8.3
  • Oracle 10 and 11
• Replace "html_p" by "mime/type" and richtext widget for input (news, bulk-mail, others?)
• calendar: localize notifications
• forums:
  • DONE: localize notifications
  • removed the SC implementation of search to avoid confusion (search now implemented with callbacks)
• assessment:
  • review daveb changes
  • added "views" support (explicit dependency)

Wish List

NOTE: xowiki was NOT part of .LRN 2.4 or earlier. Since noone from the accessibility group has checked, whether xowiki is compliant with WCAG 1.0 double-A, the DotLRN consortium board meeting decided in Valencia to include xowiki and maybe some other packages in a dotlrn-extras distribution in 2.5. This extra-distribution should not have the strong accessibility requirement as dotlrn-all, where every package must be manually checked in detail by some "accessibility expert".

Note by Don Baccus:  Honchos, not an ad hoc group of .LRN consortium members, decides what goes into .LRN.  Honchos proposed, and the board agreed, that a MINIMUM requirement for inclusion is accessibility compliance.  If xowiki hasn't been checked, by default it DOES NOT go in, not vice-versa.

New features

• Removal of .LRN applets:  see the Removal of Applet thread
• Wiki (xowiki with special policy set designed for .LRN, i.e. avoid professors writing their own tcl scripts or access the DB (DONE), probably a simplified UI?) Galileo will work on this and a few additions to have a wiki for .LRN, in late may / early june 2008.
• Content package: tools for creating content online for .LRN
• xo-S5: online presentation tool (and get rid of wimpy-point)
• Replacement of static portlets by xowiki portlet pages (need to figure out if we use the same xowiki instance for "portlet pages" and for the wiki)
• Blogger replacement with xowiki blogger? (have to review funtionality list, upgrade from actual blogger, others)

Having the idea of a macro-tool (xowiki) that can be easily customized for specific use with prototypes and others will help us to the reduce the code to maintain.

To do

• xowiki (What's missing?)
• content: produce an standard release that work atop .LRN (oracle & PG).
• s5
• xo static portlet (supported via xowiki-portlet and dotrln-xowiki; what else?)
• blogger

Packages that could be xoified?

There are packages that could be replaced with xowiki/xotcl.
xowiki might need a finer granularity (object level) for permissions (parties), categories, comments.

• news (if we manage to tell xowiki to use dates to display and archive a news item
• edit-this-page
• bulkmail (like news but with email being sent out and ui for selecting role/users)

I would even to that far to say that we can replace forums (using page_order) and calendar (similar to news/bulkmail but special UI).

.LRN 2.3 Release Management

Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 06 Nov 2016, at 10:02 AM

.LRN 2.3.1 was released Sept. 9th 2007.

.LRN 2.3.1 contains acs-core, dotlrn-all and dotlrn-extras packages. See Aliases at CVS for a detailed list of the packages included in those aliases.

Releases are coordinated by the .LRN Leadership Team. Weekly technical meetings: Tuesdays at 17:00 GMT in IRC at openacs channel.

To do and goals for release:

• Bugs fixing (a wiki page with a summary will be created): please test and report bugs at bugtracker.
• WC3 WAI WCAG level AA compliance (see Accessibility for more info)
• CSS rewrite (See Zen Project for more info)

.LRN 2.2 bugs

Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 06 Nov 2016, at 10:01 AM

Last modified: 2016-11-06 10:01:45.739891+01

OPENED BUGS

BUGS WHICH PRIORITY TO BE DOWNGRADED

RESOLVED/FIXED/CLOSED BUGS

.LRN 2.2 Release Management

Created by Carl Robert Blesius, last modified by Gustaf Neumann 06 Nov 2016, at 09:59 AM

Last modified: 2016-11-06 09:59:42.237915+01

Release Status

.LRN 2.2.1 Final has been released on January 3, 2007.

.LRN 2.2.1 use OpenACS 5.2.3

en:.LRN_2.2_bugs

List of Packages that are part of .LRN 2.2

Installed by Default (.LRN Standard Install)

dotlrn/install.xml

• en:dotlrn-assessment (applet not installed by default)
• en:dotlrn-bm
• en:dotlrn-calendar
• en:dotlrn-dotlrn
• en:dotlrn-evaluation (applet not installed by default)
• en:dotlrn-faq
• en:dotlrn-forums
• en:dotlrn-fs
• en:dotlrn-homework (applet not installed by default)
• en:dotlrn-news
• en:dotlrn-portlet
• en:dotlrn-static
• en:dotlrn-random-photo
• en:theme-selva

CVS MODULE: DOTLRN-ALL

• en:acs-datetime
• en:acs-events
• en:acs-mail-lite
• en:assessment
• en:assessment-portlet
• en:attachments
• en:bulk-mail
• en:bm-portlet
• en:calendar
• en:calendar-portlet
• en:categories
• en:dotlrn
• en:dotlrn-portlet
• en:evaluation
• en:evaluation-portlet
• en:static-portlet
• en:faq
• en:faq-portlet
• en:file-storage
• en:fs-portlet
• en:forums-portlet
• en:forums
• en:general-comments
• en:new-portal
• en:news
• en:news-portlet
• en:notifications
• en:profile-provider
• en:oacs-dav
• en:random-photo-portlet
• en:rss-support
• en:user-profile

Optional Included (Not installed by default)

CVS MODULE: DOTLRN-ALL

• en:acs-developer-support 
• en:dotlrn-admin 
• en:dotlrn-syllabus
• en:lars-blogger
• en:weblogger-portlet
• en:dotlrn-weblogger
• en:trackback
• en:user-preferences
• en:workflow
• en:xml-rpc

 CVS MODULE: DOTLRN-EXTRAS

• en:views
• en:clipboard
• en:lors
• en:lorsm
• en:lorsm-portlet
• en:dotlrn-lorsm
• en:lors-central
• en:photo-album
• en:photo-album-portlet
• en:dotlrn-photo-album
• en:survey
• en:survey-portlet
• en:dotlrn-survey
• en:xotcl-core
• en:chat
• en:chat-portlet
• en:dotlrn-chat

List of Packages that do not get the vote (will not be included)

• en:curriculum
• en:curriculum-portlet
• en:dotlrn-curriculum
• en:wp-slim
• en:wps-portlet
• en:dotlrn-wps
• en:news-aggregator
• en:news-aggregator-portlet
• en:dotlrn-news-aggregator

.LRN Installation

Created by yesten dan, last modified by Gustaf Neumann 06 Nov 2016, at 09:55 AM

Before OpenACS 5.8.1, DotLRN installations required a different installer than its base system OpenACS. There was no way for an end-user to upgrade from an existing OpenACS installation to DotLRN without loosing data, or to make hybrid installations (maybe in the future to use e.g. as well components from Project Open, etc.).

Starting with OpenACS 5.8.1 (and DotLRN 2.8.0) one can upgrade from OpenACS to DotLRN via the standard OpenACS package manager. Therefore, one easy approach to install DotLRN 2.8.0 is to install first a minimal OpenACS system and upgrade in a second step:

1. Install OpenACS 5.8.1. For details, check out openacs-system-install.


2. On the running OpenACS system
   • browse to YOUR_SYSTEM/acs-admin/
   • Click on "Install Software" 
   • Click on "Install from Repository"
   • select "dotLRN" and click on the button "Install..."

This will install dotLRN with the required core components. More packages can be installed a some later times if desired.

Install instructions for .LRN 2.5.0.

Packaged installations

For platforms like Linux/Ubuntu, Linux/Debian, FreeBSD or Windows, one can use the packaged solutions installing separate databases for DotLRN and OpenACS:

• OpenACS/dotLRN Windows Installer Installation Instructions
• Installing dotLRN on debian
• Installing dotLRN on Ubuntu
• Installing dotLRN on FreeBSD (ports)

.LRN Installation (up to .LRN 2.5.0)

Created by Carl Robert Blesius, last modified by Gustaf Neumann 06 Nov 2016, at 09:54 AM

Index

Introduction 

Installing .LRN: Using the VMWare Virtual Machine 

Installing .LRN: Using the Tarball

Installing .LRN: Using CVS

Installing .LRN: Using Debian/Ubuntu Packages

Introduction

VMWare virtual machine: simple (for a testing and evalution). Tarball: medium to hard (for a production install without source control). CVS: hard but flexible (e.g. makes it easier to update your installation from the code repository between official releases). Debian/Ubuntu: simple to medium (fast and easy install for novices, easy infrastructure deployment for professional users).

Installing .LRN: Using the VMWare Virtual Machine

to be announced. 

Installing .LRN: Using the Tarball

Before you start

Quickly read the OpenACS Installation Overview and if you still feel like you can progress start with the first part of the next section: Install a Unix-like system and supporting software

(skip the obvious portions if you are already running some unix like OS). Download the latest .LRN distribution from the .LRN repository (currently 2.4.1).

Move the tarball into your /tmp directory (replace dotlrn-2.4.1.tgz with the name of the tarball you downloaded, if you downloaded another version):

mv dotlrn-2.4.1.tgz /tmp/

untar it in that directory

cd /tmp
tar zxf dotlrn-2.4.1.tgz

Installation Process

Continue with the other sections of the installation document, but instead of downloading the OpenACS tarball mentioned in the docs (section "Unpack the OpenACS tarball" in the Install Linux and supporting software document), use the .LRN tarball you just downloaded above. This .LRN distribution includes all OpenACS packages needed to install and run .LRN. Throughout the documentation, use your unpacked .LRN tarball under /tmp/dotlrn-2.4.1 (or name of the directory you unpacked it to) instead of instead of the OpenACS tarball referred to in the documentation.

.LRN is automatically installed and configured as part of the installation process if you install using a standard .LRN distribution.

When installation is complete, restart AOLserver as described in the OpenACS installation instructions.  You'll need to wait a few minutes while dotLRN configures itself.  Reload your browser page.  If installation was successful, you'll see a login page. Use the user name and password you entered for the system administrator.  A page will come up that includes a link to sitewide administration.  Visit the link, then click on the "users" link and then approve the system administrator's .LRN membership.

Explore .LRN

Go to .LRN Administration at http://yourserver/dotlrn/admin.  Create a .LRN Community and a couple of users.

Here are some suggestions for things to check out in dotlrn:

Goto /dotlrn your "workspace". Click the "My Account" link at the top and try the "Customize this portal" link there.  Goto the admin pages for a class or community and try the "Manage Membership" link. Create a new sugroup for a class or community. Edit or create new "Custom Portlets".

Installing .LRN: Using CVS

Setting up the Required Infrastructure

The OpenACS documentation page has extensive installation instructions describing how to install needed database and webserver. Follow the instructions up until the point where you are told to download OpenACS and then continue with this document instead.

Notes on using CVS

CVS commandlines are given in terms of anonymous users, if you have an account on openacs.org, use your login where appropriate. Don't forget to set the CVS_RSH variable in your shell envrioment to "ssh".

Checking out the code

Go to /var/lib/aolserver (create the directory if it is not already present). Checkout the code (this is a complete code checkout and might take a while):

cd /var/lib/aolserver
cvs -d anonymous@cvs.openacs.org:/cvsroot login
cvs -d anonymous@cvs.openacs.org:/cvsroot -r oacs-5-4 co openacs-4
mv openacs-4/packages/dotlrn/install.xml openacs-4

Proceed

You can then proceed with the normal OpenACS installation instructions.

Explore dotLRN

Go to dotLRN Administration at http://yourserver/dotlrn/admin. Make some dotLRN users, terms, departments, classes.

Here are some suggestions for things to check out in dotlrn:

Goto /dotlrn your "workspace". Click the "Control Panel" link at the top and try the "Customize this portal" link there. Goto the admin pages for a class or community and try the "Manage Membership" link. Create a new sugroup for a class or community. Edit or create new "Custom Portlets".

Enjoy!

Automated Installation

As an alternative to the manual CVS checkout and installation described here there are scripts that will automate the install for you. See the OpenACS installation documentation for more details.

Installing .LRN: Using Debian/Ubuntu Packages

Debian

Ubuntu