Forum OpenACS Development: Re: Remaining work for 5.0.0 release

Collapse
11: Re: Remaining work for 5.0.0 release (response to 1)
Posted by Don Baccus on 12/12/03 09:44 PM
#1144 is fixed and I believe I marked it so yesterday (it was fixed a bit earlier but I forgot to mark it in bugtracker)

#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.

Collapse
12: Re: Remaining work for 5.0.0 release (response to 11)
Posted by Jeff Davis on 12/12/03 09:51 PM
I committed a fix for the calendar problem (1226), Dirk set direct permissions but did not revoke inherit so students ended up with create by virtue of create on the parent.

Hopefully that's it and once the test servers get rebuilt Lars can confirm it's ok.

Collapse
13: Re: Remaining work for 5.0.0 release (response to 12)
Posted by Joel Aufrecht on 12/17/03 02:20 PM
The following items still block the release of 5.0.0 release candidate 1:
  • 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.