Forum OpenACS Q&A: Next Release

Posted by Nima Mazloumi on
Hi all,

we had a bug bash this weekend. Result:

No prio 1 bugs for OpenACS
No prio 1 bugs for dotLRN

8 prio 2 bugs for OpenACS left
55 prio 2 bugs for dotLRN left (40 from years 2003,2004 still need to be checked)

The test system was: SuSE Linux 9.2, PostgreSQL 7.4.7, AOLServer 4.0.10, Host:, Port 9001

Also we tested upgrades:

1. OpenACS from oacs-5-1 to oacs-5-2, worked
2. dotLRN 2.1.3b1 from oacs-5-1 to oacs-5-2, worked

Steps remained:

- Check the above 40 dotLRN bugs (1)
- Test the upgraded systems (dotLRN, OpenACS) (2)

Now BOTH causes a problem.


1. oacs-5-2 has package versions older than on oacs-5-1
2. oacs-5-2 could have packages older than on oacs-5-1

Regarding 1:

Package Name, Version on oacs-5-2, Version on oacs-5-1:

Date and Time Utilities 4.1, 4.2
Attachments 0.9, 0.10
Bulk Mail 0.5.1d6, 0.5.1d7
Calendar 2.1.0b3, 2.1.0b4
General Comments 4.6.1, 4.6.2
New Portal 2.1.1, 2.1.2d2
Profile Provider 2.1.1, 2.1.2
RSS Support 0.3d6, 0.3d7
Survey 5.0.0b9, 5.0.1
User Profile 2.1.1, 2.1.2


Bulk Mail Portlet 2.1.0b3, 2.1.0b4
Calendar Portlet 2.1.0b3, 2.1.0b4
FAQ Portlet 2.1.0b3, 2.1.0b4
Forums Portlet 2.1.1, 2.1.2
File Storage Portlet 2.1.2d1
News Portlet 2.1.1, 2.1.2d2
Static Portlet 2.1.1, 2.1.2d2
Survey Portlet 2.1.1, 2.1.2d1

dotLRN Packages:

dotLRN Bulk Mail Applet 2.1.1, 2.1.3b1
dotLRN Calendar Applet 2.1.1, 2.1.3b1
dotLRN Applet 2.1.1, 2.1.3b1
dotLRN FAQ Applet 2.1.1, 2.1.3b1
dotLRN Forums Applet 2.1.1, 2.1.3b1
dotLRN File Storage Applet 2.1.1, 2.1.3b1
dotLRN Homework 2.1.1, 2.1.3b1
dotLRN News Applet 2.1.1, 2.1.3b1
dotLRN Portlet 2.1.1, 2.1.3b1
dotLRN Static Applet 2.1.1, 2.1.3b1
dotLRN Survey 2.1.1, 2.1.3b1

What we urgently need now is:

- every one stop developing on oacs-5-1
- The help of a volunteer to fix the above version problems
- The help of someone to merge all developments newer in oacs-5-1 than in oacs-5-2 to get merged to oacs-5-2 or head

We need this to do (1) and (2) above in order to be able
to release dotLRN 2.1.3 asap and even more important to
release dotLRN based on OpenACS 5.2 called 2.2 (where at
least the upgrade worked out successfully).

Can someone in the community please help?

2: Re: Next Release (response to 1)
Posted by Malte Sussdorff on
Hi Nima,

as for 1) just look who did the last commit and bug that person to merge on his own. As for 2) I have the suspicion that it will be only Joel who pumped up the version number for the release, so we should be fine (did you make a diff, just to see what changed). We could then bump up the version number to 2.2b1 for dotlrn packages from 5.2.

Other than that: GREAT WORK!!!!!

Thanks a lot for this productive weekend.

3: Re: Next Release (response to 1)
Posted by Rocael Hernández Rizzardini on
Hello Nima,

I think is worth to clarify some issues regarding openacs development, and next .LRN releases, from the openacs CVS docs:

"For non-core packages, developers should work on a checkout of the release branch of the lastest release. For example, if OpenACS 5.1.0 is released, developers should work on the oacs-5-1 branch. When oacs-5-2 is branched, developers should continue working on oacs-5-1 until OpenACS 5.2.0 is actually released."

So now all the packages are stable at oacs-5-1 and the development should continue there until 5.2.0 is released as stable. There are some exceptions for some recent packages that its development is happenning at oacs-5-2:
So no merge between oacs-5-1 and oacs-5-2 is needed right now, and in some packages is actually forbidden.

Right now, if you want to upgrade .LRN to openacs 5.2.0, that upgrade will be for the core packages only, but it is not an upgrade of the rest of stable non-packages. So taking packages from oacs-5-2 (like dotlrn, forums, etc.) makes no sense now since they are most likely unmaintained and not up to date.

What do you mean with: (1) and (2)?
Is these:
- every one stop developing on oacs-5-1
- The help of a volunteer to fix the above version problems

No version problems need to be fixed now, that will be handled when the merge happens.
Also, all the packages at .LRN has been tagged / released by Joel, so we can easily see which are the differences and if someone has added something that we weren't expeting for the next release.

I sencond Malte, excellent work Nima and his team.

4: Re: Next Release (response to 1)
Posted by Nima Mazloumi on
Alright, but what if for a package development has taken place in oacs-5-1, oacs-5-2 and HEAD. How is this solved?
5: Re: Next Release (response to 1)
Posted by Nima Mazloumi on
Rocael: I tested the upgrade of dotLRN to OpenACS 5.2 for core. What would be the next step then if we would like to use Assessment, Lors Central ... simply install them? At least for Lors Central OpenACS 5.2 is required.