Forum .LRN Q&A: Re: .LRN 2.1

Collapse
9: Re: .LRN 2.1 (response to 8)
Posted by Tracy Adams on 05/11/04 12:15 AM
Hi everyone,

No need to wait for a release for these changes, you can have them now. You can just upgrade to that OpenACS package from the APM.  Just grab those distributions.

What you won't get and we still don't have is a well-tested, well-oiled, .LRN release.  That is really going to require us to take a step back, work as a team, and go through a real release process.  (See my next post)

Collapse
10: Re: .LRN 2.1 (response to 9)
Posted by Joel Aufrecht on 05/11/04 01:01 AM
In order for automatic upgrade to work, two things must be true:
1) The version number of the bug-fixed package must be incremented.  We can use the dot release number for this.  Suppose package foo is on version 3.0 and it gets a bug fix.  It should now be 3.0.1.
2) The version must be tagged as compatible with the kernel.  Since .LRN 2.0 runs on OpenACS kernel 5.0, this means that the version must be tagged with openac-5-0-compat.  This gets a bit confusing when the bug fix is on the version of the package that's on the 5.1 branch.  It's still just a matter of tagging, but you have to be sure that the 5.1 code is still compatible with 5.0, and that the upgrade works.

If the developer does all that, then in order to get the fix, admins only need to go to the APM and click Upgrade From Repository and pick that package.  If you are running from a local cvs repository, it's a bit more complicated but it's all documented, as noted above.