/
2.5 Release Planning-19 (20080207)

2.5 Release Planning-19 (20080207)

Dec 17, 2021

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

  • Update from Capetown

  • Status of Release

  • Testing JSR-170

    • QA4-US: Ran

  • RC1

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

      %

      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. 

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