2.5 Release Planning-19 (20080207)

Owned by Former user (Deleted)
Last updated: Dec 17, 2021 by Wilma HodgesVersion comment
6 min read

Attendees

If you know you will be attending, please list your name

  • Megan May (Meeting facilitator)
  • Peter Knoop (Sakai project coordinator & regular attendee)
  • James Logan (regular attendee)
  • Renu  (regular attendee)
  • David Haines (regular attendee)
  • David Horwitz
  • Linda Place
  • Anthony Whyte
  • Jean-François Lévêque
  • John F. Hall
  • Charilie
  • Seth Theriault (semi-regular attendee)

Meeting Agenda

Notes on Discussion Points

 Update From Capetown
RC1 Tag
Review of Open/Critical List

Testing JSR-170

Release Status

  • Time line Review - Beta2 tag cut on 9th.  RC1 should be cut and deployed by the time this meeting is held
  • Progress -
    • There are over 70 bug fixes going in from beta to beta2.  We were  down to 47 awaiting verification last week.  This week there are 39 awaiting verification
    • We're seen a lot of progress in the list awaiting verification.
    • % Bugs Verified

    • Date

          1. Awaiting Verification

      # Verified

      %

      1/11/2008

      453

      720

      ~61%

      1/30/2008

      405

      773

      ~66%

  • Areas to focus on - http://bugs.sakaiproject.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11510

JSR-170 in 2.5

Summary of rationale for inclusion:   The technical merits of the proposal to merge in JSR-170 into 2.5.x were not a factor in the concerns that were raised.  Much of the discussion rose around violating our current processes (ie breaking code freeze) and the desire that changes to this process should be made in the future.  Given that the there is strong support from the development team, test plans to ensure that adverse effects are not felt, community willingness to assume the risk, community support to exercise the (experimental) code in production, and that this leverages our resources is the best way possible, that the recommendation is that these changes should be merged into 2.5.x after the beta2 tag has been cut. Rest assured, release process refinement will occur.

Testing Plan 

Steve Gitehns put up a to make sure that jackrabbit is really disabled and not doing anything. It will have to be run by someone with read access to the servers file system, logs, and database. The test plan for the JackRabbitService on the Test Plan/Scripts page on the attachments tab:

http://bugs.sakaiproject.org/confluence/display/QA/Test+Conditions+and+Scripts

In addition to compile time unit tests, Steve also wrote a small validation test that can be run against a live server to make sure it really is disabled with our deployment configurations.  There are 3 versions of it:

- A Jython script for Sash using the standard python unittest module.
(Obviously no one can run this until I get off my arse and tag another version of sash).
https://source.sakaiproject.org/contrib/jcr/disabled-jackrabbitservice-tests/JackRabbitServiceTest.py

- A Standard Sakai JWS WebService and Client that can just be dropped in.  At the moment this is probably the only thing that doesn't require installing extra stuff on the QA servers.  This is not a real JUnit check, but just checks the 5 conditions manually and reports with a human readable string.
WS:
https://source.sakaiproject.org/contrib/jcr/disabled-jackrabbitservice-tests/DisabledJackRabbitServiceTest.jws
Client:
https://source.sakaiproject.org/contrib/jcr/disabled-jackrabbitservice-tests/JwsDisabledJackRabbitServiceTestClient.py

- A TestRunner test with a real JUnit test.  (Depends on having the testrunner installed, although you can the test without the GUI, again I need to get off my behind and finish polishing up the half finished GUI for it).
https://source.sakaiproject.org/contrib/jcr/disabled-jackrabbitservice-tests/DisabledJackRabbitServiceTestRunner/

So far we're only testing that JackRabbit is disabled, will be adding some tests to make sure it's enabled and working as we go forward.  (smile)

Testing/Resources Needed

  1. Those  read access to the servers file system, logs, and database to run through manual verification (Megan can do this but would like for this to be done by others. )
  2. Someone to run validation test against live server

Longer Term

  1. When should this be flipped on for testing?

Overview of Time lines & Goals  (Standing item)

Timeline Review
  • Nov 7 tag 2.5.0.012
  • Nov 22 2.5.0.beta cut
  • Nov 26 2.5.0.beta deployed to QA network
  • January 9th 2.5.0.beta2 cut
  • January 10th deployed to QA network
  • Week of Jan 28th - RC1 cut
Goals
  • Elimination of all outstanding Blocker and Critical bugs for 2.5
  • Acceptable Performance testing on mysql and oracle databases for Assignments, Resources, Forums, GB & T&Q. What is acceptable? At this point in time, no degradation from performance experienced in 2.4
  • High degree of verification (85%) of resolved JIRA bugs
  • Confirmed functional testing on all tools.
  • Positive feedback from sites running a tagged version of off branch.

Stats on Issues Reported 

Progression

Q: How do we move from Beta? RC?
A: To make the progression from beta to release candidate, the aim is the resolution of outstanding blocker and critical bugs reported.

Q: Are we going to make the move from Beta to RC?
There are a number of critical issues reported against a 2.5 build we're not likely to get movement on due to resources being unavailable. What do we do with these problems?

A:  Some of them will be resolved in the next release or later in the maintenance branch.  These items should have a target version set and include comments in the rationale as to why they can't be resolved now.

Meeting Notes

Update from Capetown
Smooth sailing, but running into another JSF version issue. Stephen working on some test scripts. Testing some patches from Ian on Search, before going life.

Status of the release
Anthony: Artifact creation process is different now with Maven 2. Using maven 2 release process. Andrew might create a mirror set of repositories for testing against, before running the live releases (since this is the first maven 2 release).

Renu: Have closed 4 issues with podcasts, polls, and emailing to wrong id. Opening a few new tickets with mail tool. SAK-12750, SAK-12703

James: Focusing on some internal testing (assignment2 and gradebook) Should be able to get back to verifying release things once new release is up.

John Hall: Looking at blogger javascript

Haines: No report.

Linda: Testing resources that was backported to 2.4.x. Seeing a roughly 5% improvement across the board.

JSR-170 Testing

Georgia Tech has been running the validation tests fine. Clay is going to do the manual verification today.

Open Critical and Blocker issues:

SAK-12921 - Getting issue details... STATUS : Some of the QA servers haven't been fully configured for OSP at the moment, so this might be a non-issue.

SAK-12820 - Getting issue details... STATUS : Mike is going the accessibility list to come up with a top 5 set of issues to get fixed. (as long as a long term top 5 for 2.6). Will wait to see what Mike says on this one.

SAK-12773 - Getting issue details... STATUS : David will check with Greg in morning. Lydia can't reproduce this in the QA environment at the moment.

SAK-12754 - Getting issue details... STATUS :

SAK-12682 - Getting issue details... STATUS : Ian has been working with Cape Town on this one.

SAK-12626 - Getting issue details... STATUS : Waiting to hear back from Stephen

SAK-12148 - Getting issue details... STATUS : Karen and Daniel are working on tracking down the environment cause. Only happens the first time the server starts up.

SAK-12000 - Getting issue details... STATUS : Josh is working on getting the appropriate environment to reproduce it.

SAK-11875 - Getting issue details... STATUS :

SAK-11798 - Getting issue details... STATUS : In progress but probably won't be resolved until after release

SAK-11783 - Getting issue details... STATUS : Probably not resolvable for 2.5.

SAK-11636 - Getting issue details... STATUS : Megan will touch base with Ian.

SAK-11628 - Getting issue details... STATUS :

SAK-11411 - Getting issue details... STATUS : Doesn't apply for the release, not in build

SAK-11199 - Getting issue details... STATUS : Analysis still going on for problem. Likely addressed in future release.

SAK-11098 - Getting issue details... STATUS : David notes this one at beginning of call. Hopefully fixing the JSF version helps. Stephen has attached a script.

SAK-7670 - Getting issue details... STATUS : Probably get updated in a maint rlease

SAK-7637 - Getting issue details... STATUS : Joe has been working on the site version, and hopes to have made some advances that help the My Workspace version as well.

Discussion

Scheduled to release the week of the 20th. Seem to be hovering around 20 issues. Some blockers that definitely need to be wroked out, but think we should be able to press ahead with the release.

Micheal: The process has worked itself out well, thinking about a dot zero release on the 20th, with maintenance in 6 or so weeks.

Megan: We can probably continue to take fixes if they are tested by Capetown.

Horwitz: Most of the new merged fixes coming in are pretty small fixes, the kind of things we should be focusing on for this sort of thing.

Haines: Did we decide these are all really blockers.

Michael: Assuming we are going to make progress on this FCK Editor. Not sure if the Samigo startup issue is really a blocker.

Only happening on QA-1 UK right now.

( moderate length discussion of 12148 )

One outstanding licensing issue Megan is working out.