2.5 Release Planning-16 (20080117)

Owned by Former user (Deleted)
Last updated: Dec 17, 2021 by Wilma HodgesVersion comment
7 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)
  • Steve Githens (scribe)
  • James Logan (regular attendee)
  • Renu  (regular attendee)
  • David Haines (regular attendee)
  • Jim Eng (regular attendee)
  • Seth Theriault (regular attendee)
  • David Horwitz
  • Linda Place
  • Anthony Whyte
  • Ian Boston

Meeting Agenda

  • Status of Release
  • Testing JSR-170
  • Consideration of FCK 2.5.1 in 2.5

Notes on Discussion Points and Meeting Notes

Release Status

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?

Consideration of FCK 2.5.1 in 2.5.0 (SAK-12542)

Josh Ryan has completed implementing the latest version of FCKeditor and has requested the community's input on inclusion in 2.5.   There are a few good benefits, such as support for the new version of Safari (finally) and fixes for the following issues

  • SAK-7007
  • SAK-5986 
  • SAK-8654
  • May resolve SAK-12000 (need someone to test this in trunk)

The elements nessesary for this include

  1. Resources is needed to update the test plan
  2. Someone should run through the test plan on nightly prior to merge
  3. Community consensus for inclusion

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.

Where we stand

Issues Reported against just 2.5

2.5.0.013

2.5.0.beta

2.5.0.beta2

2.5.0.rc1

2.5.0.rc2

Blocker

4

3

 

 

 

Critical

20

14

 

 

 

Total

24

17

 

 

 

2.5.0.beta Blockers - one documentation, two recently opened

2.5.0 Beta Critical -  There are 3 that we do not have anyone working on (SAK-10487, SAK-11798, SAK-12056).  One of those is related to performance in Forums as well as another that was unassigned. 6 reported in the  last 2 weeks.

All Outstanding tickets (just bugs, no tasks)

2.5.0.013

2.5.0.beta

2.5.0.beta2

2.5.0.rc1

Blocker

3

3

 

 

Critical

58

55

 

 

Total

61

58

 

 

Changes in 2.5.0.Beta
34 tickets - as with the .13 tag, most with Assignments

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

Overview from David at Capetown, our 2.5 piloting university:

So far things have gone pretty smoothly. Have about 30% of our normal load. Feel pretty confident about running it in production. More so than 2.4. Outstanding issue is search, Ian is resolving right now.

Megs: Any other major bugs besides the forum issues?

David: Sudden spike in forum problem tickets. Trying to figure out if they are returning issues or new issues. Have a couple things to try out.

Call for extra agenda topics:
Would it be able to encourage the developers working on the projects in the pom.xml. Can that be done for 2.5 still or would that have to wait for 2.6.

James: Is there a server that is running the citations tool? We've seen some issues on QA-4

Release Timeline:
Cut the beta 2 tag on the 9th. We are on the beta tag. Will cut the release candidate the week of January 28th. A few weeks later will have a release.

Keep working off the QA workgroup filter.

Updates from testers:

Jean François: Not sure how much time can put into it the next few weeks. Not familiar with a lot of the tools, so it took a while to get up to speed. Corresponding with folks on a few of the issues.

James/Renu: Closing some issues. Citations Helper, which test servers are available with the citations helper probably configured? (Until we have it configured).

The Sakaibrary folks tend to test on different smaller servers, Megan will talk to them to see if we can use them. Perhaps email the QA list.

Have also been testing the assignment issues, all appear to be working.

David Haines: Running post 2.4 branches of assignments.

David Horwitz: Mostly running 2.5 branches at the HEAD of the branch.

Linda: No changes in code since we did the assignments test. Ready for doing a drop box test. Ran a baseline against 2.4. (Not great results with on that)

Jira Rundown

SAK-12727 - Getting issue details... STATUS Search. Ian can reproduce, progress is occurring

SAK-12000 - Getting issue details... STATUS Many folks involved in testing and reproducing. Pasted word text not coming through correctly. Josh Ryan can't reproduce it, and would like someone to test it on Nightly and hoping that latest upgrade fixes it. Georgia tech will try this out again.

SAK-12565 - Getting issue details... STATUS Help Documentation. David and Stephen will report back on this one.

SAK-11411 - Getting issue details... STATUS Transformable / Preferable Module in contrib. When we switched from M2 to SNAPSHOT then it must have stopped building (the UI part in contrib)

SAK-11141 - Getting issue details... STATUS Chen is going to start looking into today should have fix before RC1

SAK-8421 - Getting issue details... STATUS Forum Stats are slow. Looks like some indexes are being updated.

SAK-7670 - Getting issue details... STATUS Georgia Tech is working on a patch? Peter will email Clay about it.

SAK-12148 - Getting issue details... STATUS Reported from UK-1, not up to date at the moment, checking on the server

SAK-12665 - Getting issue details... STATUS Ticket will hopefully be resolved Monday

SAK-12570 - Getting issue details... STATUS No comments Megan will up on on this and 12665

SAK-12712 - Getting issue details... STATUS Wiki has a few strings that aren't externalized Ian will try to fix this in the next week.

SAK-11636 - Getting issue details... STATUS It would be great if we could get a patch for this one to apply.

SAK-8791 - Getting issue details... STATUS No way to remove folders. Old problem popping up again. Peter will touch base with Jim on this one

SAK-12603 - Getting issue details... STATUS Josh is working on it. Megan will ping him

SAK-7637 - Getting issue details... STATUS My Workspace Synoptic Forums is super slow. Capetown adds this by default to folks workspaces. We don't think this will be resolved until 2.5. Megan will talk to Lance about resources for this. Will be a problem for UM as well.

Not much resources from IU right now for this one. We might need to look elsewhere to get work on this one.

SAK-12701 - Getting issue details... STATUS Capetown is getting lots of tickets for this.

SAK-12567 - Getting issue details... STATUS Dialogue in process with bug reporter.

SAK-11875 - Getting issue details... STATUS Still being investigated

SAK-12626 - Getting issue details... STATUS Assigning back to reporter to get more information about problem.

JCR-170 Testing
January 28th the JackRabbit will be merged on to the QA servers. Steve G will work with a few of the QA Admins to verify the disabled test plan ( requires the admin to look at the directories on the filesystem ) .

Longer term testing. For the 2.5 release just verifying no impact is enough, going forward, we will obviously need tests to test it working.

Upgraded WYSIWYG for 2.5:
It sounds like folks aren't comfortable upgrading to a new version of FCKEditor until post 2.5.