Forum .LRN Q&A: Re: .LRN 2.0.3 just needs to be tested

Collapse
Posted by Nima Mazloumi on
Maybe we can even release together with OpenACS 5.1. What do you think?
Collapse
Posted by Tracy Adams on
Here is the situation.  We have 2 things activitely happenning in the community.

1) People are trying to launch/upgrade using the 2.0 releases (2.0.2, 2.0.3, etc).
2) OpenACS is working on 5.1 which contains over 100 bug fixes. (Note that the release of .LRN 2.0.3 will not contain any of these fixes since .LRN 2.0.3 is on the .LRN 2.0 branch)

The idea for the 2.0.3 release was to help people in situation 1 get over any critical bugs that may be preventing them from launching or upgrading.

After OpenACS 5.1 is release, we can release a new version of .LRN that contains the OpenACS 5.1 fixes and anything else in the meantime.

Perhaps the criteria, then, for any of the newly found bugs in this thread is "Is it critical for anyone who is launching or upgrading".  If so, we wait and put in the release. If not, we put it in after OpenACS 5.1.