Forum .LRN Q&A: .LRN 2.1 plan

Collapse
1: .LRN 2.1 plan
Posted by Tracy Adams on 09/10/04 06:29 PM
Hi everyone,

Here is the plan going forward for .LRNv2.

a) Sloan and Galileo are working on performance issues on their Oracle and Postgres installations.  We'll continue to fix these and submit them to the core.
b) Once we have the performance issues stabalized, I'll cut a beta tarball.
c) We'll collect critical issues in the tarball and make a list of what we need.
d) We make the fixes.
e) We do the release candidate.

Institutions interested in using .LRN 2.1 should be ready to install the beta against and export of their database and test the beta extensively in order to participate in steps c and d.  Otherwise, you'll "miss the boat" so to speak...

Collapse
2: Re: .LRN 2.1 plan (response to 1)
Posted by Nima Mazloumi on 09/11/04 09:47 AM
"Institutions interested" does this apply to those already using 2.0.3 or only for new installations?
Collapse
3: Re: .LRN 2.1 plan (response to 2)
Posted by Tracy Adams on 09/12/04 12:52 AM
Hi Nima,

Everyone (both 2.0.3 and 2.1) should check out 2.1 beta, try out a test upgrade, and make sure the new software meets their needs.

Collapse
4: Re: .LRN 2.1 plan (response to 1)
Posted by Rafael Calvo on 09/13/04 04:53 AM
Tracy,

We (Sydney) will be upgrading to 2.? in the (australian) summer vacations November-January.

cheers

rafael

Collapse
5: Re: .LRN 2.1 plan (response to 1)
Posted by Rocael Hernández Rizzardini on 09/17/04 12:44 AM
We would like to add a last minute feature before going beta, which is allow notifications on news, blogger & general-comments, those are important improvements, straight forward changes and are well tested.
Shall we commit?
Collapse
6: Re: .LRN 2.1 plan (response to 1)
Posted by Rocael Hernández Rizzardini on 09/17/04 05:59 AM
Also, we are working towards enhancements on:
/admin/users (looking at a given users is practically impossible for big installations when the user has lots of contributions)

/dotlrn/admin
also, several pages there are not scalable at all

if someone else is working on this, pls let us know.
more specifics on this comming...