Forum OpenACS Q&A: OCT Meeting 11-12-2003

Collapse
1: OCT Meeting 11-12-2003
Posted by Malte Sussdorff on 11/13/03 12:58 PM
  1. Attendance:
    • Attending: Lars, Malte, Til, Jeff, Caroline, Dave, Don
    • Unavailable (announced): Peter
    • Unavailable (unannounced): Roberto (I might have missed him saying he can't attend)
    • Notetaker: Malte
  2. Release issues.
    • A beta release of OpenACS 5 and .LRN 2.0 has been made. Check out the release criteria why we did this.
    • Jeff agreed to be a bug czar for the month of November. The responsibilities are as follow:
      • Look at all Open (currently 220) bugs and check the severity settings and if they are stoppers for the release. Assign to 5.1 for bugs not fixable for 5.0
      • Apply patches
    • The release will be made under the following terms:
      • All sev1 and sev2 bugs have been fixed.
      • A release candidate will be cut once we have all sev1 and sev2 bugs fixed. If we don't find any more bugs (in these catogories), the release will be made
      • Timeline will be 1st of Dezember for RC1
    • Upgrade scripts will only be provided from full release to full release,not between alpha and beta versions.
    • Testing the upgrade of 4.6.3->5.0 is necessary and considered a showstopper for the release, if not working. Don and DaveB will take care of it:
      • Dave is the lead in this and is setting up a automated upgrade server that will test the upgradability automatically. Not sure exactly how this will work yet. It involves using the automated install script along with tclwebtest to test the upgrade process.
      • Don will hack up the changes to the bootstrap code once Collaboraid tells us exactly what needs to be done to upgrade authentication code so the sysadmin can log into their site, but dave's doing the actual setting up of the server.
    • Automated testing for the API is highly recommended. Automated testing using tclwebtest will be investigated by Peter and Tilmann for the 5.1 release
  3. OCT related issues
    • The maintainer idea will be dropped. People can say they'd like to act as default assignee on the bug-tracker. Whoever is working on a package is going to be the "maintainer" for said period of time
    • Worker bee tasks will be assigned if the bug czar or someone with requisite knowledge has decided it is a bug solveable by the average community member. It should encourage people to pick it up
    • An enhancement to bugtracker for saying "I'm working on it" would be appreciated.
    • OCT forum vs. Private email vs. Openness of the OCT. One hour of discussion between some people will not be summerized. They can feel free to summarize their points in an open thread in the Forums.
Collapse
2: Re: OCT Meeting 11-12-2003 (response to 1)
Posted by Joel Aufrecht on 11/13/03 02:40 PM
On item 3, last bullet, I believe there was agreement (or lack of dissent) that all email sent to mailto:oct@openacs.org should be auto-posted to an OCT forum, like we already do with cvs checkins.  It was not directly addressed whether this forum would also be used for direct forum posting by OCT members.