Forum OpenACS Q&A: OCT meeting 11-19-2003

Collapse
Posted by Malte Sussdorff on
First of all, sorry for the delay. I got into a hostage situation yesterday (literally spoken).

Attendees

Release status

  • What do we need for the release ?
    • things between us and finishing 5.0 beta testing: 1 crit bug, 5 severe bugs, 5 broken auto-tests, 1 install logfile error
    • things fuzzily between us and 5.0 beta complete: 4.6.3 upgrade script; more testing
    • A general release criteria is that a RC shall be up for a week without any SEV1 bugs comming up.
    • The idea of a vote by the OCT for a release has been abandoned. The release manager will make the final call on when to release (though announce it a little bit in advance).
  • Autotests: There are at least one for each core package, though some are broken. As per Don's suggestion for broken tests we add a comment in the test that references the bug number and reference the test in the bug report, and whoever fixes it cleans up report and source.

Upgrade Status (4.6.3 -> 5.0)

Dave said he did not make as much progress as hoped, so no new status was available. Next week the auto-install scripts should be working and a status report on the progress will be available. Thanks go out to Andrej Popov for detailing the tedious task in the first place.

Transperancy

To open up oct@openacs.org will be mirrored in a forum. To keep secrecy possible (e.g. in case of security leaks) a second mailinglist oct-secret@openacs.org will be setup. Steps as agreed upon:
  1. create an OCT forum
  2. someone setup something that pipes email to oct@openacs.org to the OCT forum
  3. we setup an oct-secret@openacs.org mail alias which does not go to the forums
Step number 2 will happen once we have openacs.org running on 5.0.

Bug bashing session in Hamburg

A bug bashing session will happen on 24th / 25th of November in Hamburg, Germany. Attendees will be: Lars, Peter, Malte, Timo, Dirk, Björn and Joel.

We will be hanging out on IRC during that time and encourage everyone to participate remotly in getting us closer to release.

Subsite vs. Community

In a quick and swift decision we decided to call it Subsite. Tilmann made the necessary changes.

Meeting Ends