Forum .LRN Q&A: How to patch .LRN 1.0.1 without prevent upgrade to 2.0

Collapse
1: How to patch .LRN 1.0.1 without prevent upgrade to 2.0
Posted by Joerg Winckler on 10/07/03 10:28 AM
We have been running a .LRN pilot at  the University of Applied Sciences in Heilbronn in Germany and are interested in patching our system with recent bug fixes without interfering with the upgrade path from .LRN 1.0.1 to .LRN 2.0. What are important things that we must be
careful about and are there any documents that someone can share?
Collapse
2: Re: How to patch .LRN 1.0.1 without prevent upgrade to 2.0 (response to 1)
Posted by Jade Rubick on 10/08/03 07:07 PM
Are you using CVS?

The biggest thing is to use CVS. Look around for CVS documents on vendor-branches. I believe that's what you need to look into.

Be really careful with anything that affects the database. Database changes are more serious than code changes, in some ways.

Perhaps others can provide more..

Collapse
3: Re: How to patch .LRN 1.0.1 without prevent upgrade to 2.0 (response to 1)
Posted by Joerg Winckler on 10/09/03 08:13 AM
Thank you for the hint.

I assume that there are multiple branches, e.g. one for the patches and one for the ongoing implementation of new functionality.

How do I address the more stable one?

Regards,

joerg.