2.4 Release Planning-2 (20070321)

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

Agenda

  1. Status of Tool promotions (i.e. contrib migrations) - Lance
  2. sakai.properties
  3. OOTB settings
    • Cal Sum. This was made Core in 2.3 just isn't enabled by default.
    • Discussion to hide legacy Discussion tool to make Forums tool the default threaded discussion tool - Lance
  4. TOPIC FROM LAST WEEK: refactor of DB - follow up conversation
  5. Review of Chat2
    priority type key summary created updated status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  6. Resources/Sakaibrary
  7. Review of Open reported problems of concern

Notes

Participants: Megan May, Andrew Poland, Hannah Reeves, Lance Speelmon, Daisy Flemming, BU (Bob, Kathy, Soo, and Melissa), VT (Dawn Eckert & Marc Z.) Thomas A- UCD, UMich (Jim, Chuck, Gaurav, Sean, Sheeba)

Status of Tool promotions (i.e. contrib migrations)

  • Two tools have been migrated from contrib - User Membership and Polls. These were easier to migrate as the teams weren't concerned about moving over the revision history.
  • Page Order Helper: Lance has been speaking with Josh about this. Don't believe it's large enough to be a top level dir. Were thinking about site or site-manage. Group concensus was to place as a sub modulare in site-manage.
  • Migration of PageOrder and MailTool should be done by end of day. Andrew will need to update the externals once this is done.

sakai.properties

  • Everyone was asked to review what is currently in there to see if there are adjustments that need to be made

OOTB Template Changes

  • Megan pointed out that Cal Sum was added as a Core tool during the 2.3 release, but OOTB still requires admin intervention (ie an admin must use the Sites tool to add Cal Sum to a particular tool). Going forward, the templates need be adjusted accordingly (ie included in a sites Home tool). Someone spoke that they usually fulfilled requests to place this on the Home page of user's MyWorkspace as well as Site. Suggestion was to position these on the top of the home tool. To clairfy, no script/job will be in trunk to add these to existing site. Andrew Poland will provide a quartz job in contrib that people are welcome to use. This should be mentioned in the release notes. Megan will create JIRA - Glenn is the appropriate party to make this change.
  • Lance Would like to make Forums the default threaded discussion tool in sakai rather than the legacy DF. Code will not be removed, but Discussion will be sleathed in the demo by default.
  • Assignments with no grades will be stealthed in the demo.
  • Need someway to group the OSP components in the demo. Talked about adding a prefix to the tools. However, Dawn pointed out that some implementations will have course or project sites that have select OSP tools. That would be rather strange if only a set of tools has a prefix. No specific action planned at this time, but will continue to investigate options
  • Be sure that the User Membership is added to admin site.
  • Job Scheduler - Andrew pointed out that this has been included for over a year. Is there a reason it's not listed on the Admin site? It was agreed to add this as well.

Chat1 vs Chat2 - the Final call on this

  • Megan: There was a lot of discussion on the dev list about the decision for this. Today's let's figure out what the best course of action is. At one point it was suggested that we have the legacy chat along with "chat2" in the build. This just isn't practical for testing purposes. A final decision on this needs to be made and announced.
  • Suggestion made to take 2.3.1's chat and synoptic view of chat and put it into contrib. This will be something that needs to be noted in the release notes with a pointer. That tool will be called deprecated chat.
  • Andrew, Lance will work to move code over and ensure it works. Chuck offered to assist.
  • We need to do some clean up in JIRA as the old Chat bugs won't apply to the new tool. Megan will contact Peter in regards to this

Resources/Sakaibrary Update

  • Jim found 15/16 JIRA's right after code freeze when he went through the code. He's fixed a number of these items and should have them all addressed by the 28th.
  • Megan expresses concern over getting these fixed as there is a lot of functionality that can't be tested until these items are address. Could be problems.
  • As for Sakaibrary, this requires hooking into institutional DB's so IU and UMich will host servers and do this testing. Will be off OOTB. Might have Google Scholar Search, but this is something that they are waiting to hear back from google on.

Testing Update

  • Builds only been available for a couple days, but there are a number of tickets that have been reported AND resolved. Going to go ahead and but another tag this afternoon so we can test with the latest and greatest code. Tags will be created
  • Dawn has been testing OSP. There are some problems with Oracle that are being looked into.
  • Megan reports some errors in Message Center related to an oracle backend. Also, noticed that when navgating between a site & My Workspace, she sometimes gets a site unavailable error. Dawn reported experiencing similar behavior; Megan will create a BUG

Other

  • What are the recommended platforms for testing? For instance, IE 7 is new, but some tools like Resources included special code to handle IE6 rendering problems. AT IU we always recommend using the latest and greatest browser. What do others typically do? Isn't there documentation that recommends a certain browser? (YES in Sakai KB: https://www.indiana.edu/~sakaikb/display.cgi?docid=asxg). Suggestion was made to include what it was used for testing in the release doc. Megan will recommend testing FF2 and IE 7 to QA WG
  • unstealthed tools in demo? Further discussion on this point. Is it really worthwhile to do this in demo? Decision to display all tools only in DEMO version
dynamictasklist: task list macros declared inside wiki-markup macros are not supported
dynamictasklist: task list macros declared inside wiki-markup macros are not supported