2.2 Release Planning 6-7-06

Owned by Former user (Deleted)
Last updated: Jun 08, 2006Version comment
4 min read

2.2 Release Planning 6-7-06

Time: 11-12:30 am Eastern
Call information: 734-615-6805, pass code 0247.

Attendees

Chuck Severance, Lance Speelmon, Megan May, Kevin Brokamp, Peter Knoop, Chris Coppola (via IM), Clay Fenalson, Nihar Nibar, Steven Githens, Seth Theriault, Derek Ramsey, Peter Knoop, Sean Demonnier, Glenn, Pat Kava, Seth, John Leasia, Thomas Amsler, Kate Ellis, Jon Gorrono, Jim Eng and Dawn Eckert

Agenda and Notes

I. Resources

  • .004 Three outstanding issues. 1 is complete, the other two may be by the time the RC is tagged.

II. Samigo

  • The code is ready for .004 tag. Deadlocks should be resolved.
  • Question: Are fixes for Samigo going to be retrofitted into 2.1.2? Answer: We've talked about this. We'll test on .004 for the next week. Margaret will coordinate a load test similar to the ones performed for 2.1.2. We'll see how things are looking before we add this code to the 2.1.x branch.

III. Schedule group awareness
Glenn - sending out policy on group awareness. Announcement should be good with that
Schedule and Assignments.

IV. OSP testing

  • Dawn - Testing is pretty much on hold as a lot of OSP relies on Resources. Things are pushed back a bit - not sure what bugs they will have to deal with once they are able to test.
  • Lance (with Chris on IM) - OSP needs more testing time as they need to ship a product that has minimal defects

V. Code freeze - why has this not occurred?/ VI. Length of QA cycle

  • Megan: we are not currently testing a stable code base. IMHO, the release date needs to be moved out quite a bit.
  • Megan: It's not anyone's fault but developement has been ongoing. This makes it difficult to test - espcially when entire tools are completely not ready. Question: When code wasn't ready, why wasn't it moved to a branch? Answer: It would have been more work to do this so it was decided to press forward.
  • It was suggested that a code freeze did occur and now they are fixing things.
  • Point was made that it makes it hard for testing when tools are not in a testable state.
  • Daisy: Samigo needs more than a week. Lydia and Daisy were hoping for at least another week of testing due to hibernate change.
  • Glenn: Is there a reason we need to decide today? What does it matter if we cut now or later?
  • Seth: This is a product - we need to have quality, people running this with real users and the stakes are real. In addition it needs to be stable to attrack more institutions to the community.
  • Megan: It is not solid. How can we release in this state?
  • Lance: Suggested a July 15th release as the latest point in time
  • John: Is the 14th date choosen b/c OSP needs that long. Answer: It is a consideration but many of the tools need further testing
  • Chuck: June 30th won't be enough time, the 15th seems reasonable
  • 14th was choosen as the 15th is a Saturday
  • Need to make a callout to community - if you want to run 2.2 in fall, you should start testing it now. We will have new version before Aug 1. At .005 can we say that the schema/conversion scripts will be ready. Action Megan will do this
  • Poll was made of group at conclusion of conversation and all seemed in agreement to push release date out.

a. Choose a date schema/conversion scripts will be available
.005 tag
b. Choose a date to stealth tools
We spoke about doing this two weeks early and somehow came up with July 5th. However, further reflection on this shows this shoud be done on June 28
c. Choose a date to make the final cut (with few days for testing that)
July 12th. Will be .009 tag. Release would be .009 tag plus minor documentation changes
d. RC days
Will be cut on Wednesdays

VII. JIRA Items - review of Blockers and critical bugs

  • SAK-3717: John will check with Joanne on this. Not a new regression in 2.2 but it occured at somepoint in the past
  • SAK-4324: Daniel Parry has attached a patch for 2.1.2
  • SAK-4629: Jim believes this is resolved. John will test it
  • SAK-5112: Glenn is assisting Joanne. Peter advised Glenn that Joanne was waiting to hear back
    ( SAK-4422: Link this samigo bug to SAK-4372

Misc

  • Peter leaving on the 17th for vacation.

Message Sent to Dev and QA lists

Subject: 2.2 Release Update
Good afternoon,

Today during the release meeting the group consensus was to push the 2.2 release date back to July 14th to ensure that the software is adequately tested. The schedule is as follows:

  • .004 tag cut today @ 4pm. Future tags will be created on Wednesdays
  • July 5 or the .008 is the point in which provisional tools will become stealthy
  • The final release will be the .009 tag (cut on July 12) plus documentation changes (a .009+ tag)

Release meetings will continue to be from 11-12:30 Wednesdays except for June 14 and July 12 which are from 12-1 (Eastern). I will post today's meeting notes later this evening.

Those institutions planning on implementing 2.2 in the close future (Fall Semester in the states, Spring other places) are encourage to begin their local customizations. The schema/upgrade script should be ready by the .005 tag. To my knowledge, the only institutions that will be implementing 2.2 in the fall are:

  • Cambridge
  • Northwestern
  • University of Cape Town
  • IU - taking the plunge this Sunday
  • NYU - tentative
  • U Michigan - tentative
  • UFP - tentative
  • Foothill College - tentative
  • Boston U- tentative

Up to date list of of those implementing 2.2

If you belong to or know of another university that is planning to implement 2.2 in the fall, please let me know.
Questions? Comments? Concerns?
Megan