• 1 Sev 1 bug must be fixed and 12 Sev 1 bugs must be verified.
• 5 Sev 2 bugs must be fixed, and 8 Sev 2 bugs must be verified.
• 39 Sev 3 bugs could be fixed, and 50 sev 3 bugs could be verified.
• 5 failing autotests need to be fixed. Some of these tests have been checked in in anticipation of upcoming fixes, which is great. Happily, these tests link to the relevant bugs in their descriptions, a practice which we are making standard going forward.
When we achieve this, we can release 5.0.0rc1. The criteria for judging and rc release to be Final are a bit skimpy; two were discussed in the last OCT meeting, including an OCT vote of approval (rejected) and requiring that an RC tarball be up for a week without any new Sev 1 bugs found before it is declared Final.

1-Critical

1231: Notifications fails to install on oracle (found today - I am working on this one now)

• 1144: users duplicated in cc_users (Lars, Don, Dirk looking at it).
• 1226: .LRN class members can create/edit/delete calendar items (assigned to Dirk)
• 1117: www/admin/permissions-user-add.tcl does not scale (Lars looking at it)
• 857: Logger broken on Oracle (maybe shouldn't be blocking).
3-Normal/Priority-1
• 1215: class event not found in calendar.
• 1172: Creating a guest user no longer works.
• 936: acs-lang Package documentation is confusing. Probably should not be treated as blocking.
• 929: Relative Linking does not work in Versionview (file storage bug). Not sure what the status on this one is.

(We did not have a formal vote so that is of course my interpretation, but you can look at the irc log).

Anyone with an existing 4.6.x site who can try an upgrade would be great! We want to test a base 4.6.3 install upgrade to 5.0, but testing with real data would also be helpful.

#1172 has been bounced back to Peter Marklund for either some explanation or a fix depending on what he wants to do.  The code's a bit convoluted, apparently because it is used elsewhere, not just by the add-one-user code, and I figured he could tell me what's going on much more efficiently than I can try to figure out what's going on in that code.  The bug's obvious, what's not obvious is how to fix it without breaking other chunks of code that call upon it.

I think Dirk was going to revisit the calendar problem, which he thought was fixed.

• Creating a guest user no longer works.. A fix was committed today; if it is not to the submitter's satisfaction, I suggest we demote the bug to not being an OpenACS blocker (it's a dotlrn bug anyway).
• Translation server. The code to make upgrades easy and safe has been committed. Remaining work is
  • an intermittent failure in the automatic tests must be tracked down and fixed
  • The translation server has to be updated with the new code and then new translations have to be merged back.

  A conservative ETA for this work is early January.

  • Upgrades. As far as I know, several people have upgraded successfully; in each case it has taken several days and many manual steps plus some bug fixes. I would say that we have not met our upgrade criterion yet.

• all the core packages have upgrade scripts. I have defined five different levels of strictness for this criterion, and will put this on the table for the next OCT meeting, followed by a vote or TIP.
• All Severity 1 and Severity 2 bugs fixed or postponed and Test team verifies no blocking bugs. Done. (Thanks everybody!)
• All core packages have automated tests, not necessarily complete, and pass the tests. The number of failed test cases has been creeping up, and as of today we have 24 failed Oracle test cases and 6 failed PostGreSQL test cases. Due to cascading and related errors, these probably represent 4 and 3 different issues, respectively. I believe that we can punt on all of these:
  • One test is for bug 1144, which is punted
  • ad_html_to_text_clipped_link fails, but it doesn't seem critical
  • acs_templating group_tag fails, but it doesn't seem critical. Bug 428.
  • Some of the acs_lang upgrade tests fail on Oracle but not PostGreSQL. Initial inspection suggests that these would require refactoring acs_lang to add a better multi-field primary key to one of the upgrade tables. Failure to fix this shouldn't block release, especially since we've explicitly voted that translation server isn't a blocking issue.

1. the acs-kernel 4.6.5-4.6.6 upgrade script gave 2 errors which seem unimportant:

   ERROR:  duplicate key violates unique constraint "users_pk"
   ERROR:  relation "admin_rels" already exists
   

2. the acs-kernel upgrade 5d7 to 5d9 script gave me a couple errors because it couldn't drop 2 tables. Moving the 2 'drop table' commands to the end of the file fixed that.
3. The first time I tried to login, the login form bombed with the error: "can't read 'defaults': no such variable" inside template::form::create. Restarting the server again mysteriously solved the problem.
4. Upgrade failed for static-pages (can't insert duplicate key into apm_package_versions) and acs_messaging (couldn't find a function acs_message__new to drop). I didn't look into fixing the static-pages error, but commenting out the 'drop function' in acs-messaging's upgrade 4.62-4.63 script allowed it to upgrade. Looking further, I think my site was at acs-messaging version 4.6.3 in the DB, but the .info file reported 4.5, thus causing this error.

I also note that I didn't need to load the postgresql.sql file. pg_dump seems to be fixed, at least in 7.4.

[joela@samoyed joela]$ cd /var/tmp
[joela@samoyed tmp]$ cvs -d /cvsroot checkout -r oacs-5-0 openacs-4
cvs checkout: in directory openacs-4:
cvs [checkout aborted]: *PANIC* administration files missing
[joela@samoyed tmp]$

I hit this error for dotlrn, so I didn't make dotLRN 2 RC1:

[joela@samoyed dotlrn-packages]$ cvs -d /dotlrn-cvsroot checkout -r dotlrn-2-0 dotlrn-all
cvs checkout: Updating bboard-portlet
cvs checkout: failed to create lock directory for `/dotlrn-cvsroot/bboard-portlet' (/dotlrn-cvsroot/bboard-portlet/#cvs.lock): Permission denied
cvs checkout: failed to obtain dir lock in repository `/dotlrn-cvsroot/bboard-portlet'
cvs [checkout aborted]: read lock failed - giving up