2.4 Release Planning-1 (20070314)
DATE: March 14th
TIME: 12-1:30 PM
AGENDA TOPICS
Decision on final Tool Promotions
Proposed Schedule
Date to branch: proposal of March 29
Tags created Wed after meeting
Time to have daily countdown meetings in prep for release
conversion script - gentle prodding of the dev community
Configuration of QA servers
Special properties
new additions to OOTB config
refactor of DB - follow up conversation
Chat
NOTES
Tool Promotions- Contrib to Provisional
IMS TI: No, but pinging lead
Mail tool: Yes.
During meeting, it was clarified what some of the responsibilities of a provisional tool was (for instance testing until QA plan is in place). Team was going to meet afterward to ensure they were able to support the move to this status.
Will participate in testing until beginning of april when they have a TP available
Will be a part of next accessibility review
The docs(java and help) will be done by code freeze
PageOrderHelper: Yes
Polls: Yes
Preferable: Not running in prod anywhere.
Site Stats: No
Still are scalability concerns
User Membership: Yes
still needs TP, but matrix indcates that the dev of one isn't a prob
this is an admin tool that needs a new API prior to introduction to CORE status. There are a # of JIRA's requesting this: SAK-6792. SAK-6793, SAK-6794
Tool Promotions- Provisional to Core
Message Center: Yes
Post'em: Yes
Podcasts: NO
Not running at enough places in prod.
Some discussion about the marketing value of including this ootb. It was decided that we would separate the tie of provisional/core status from the tools that are exposed in the demo distribution. All tools will be available in this version
Indiana will update Maven goal.
Roster: Yes
Misc Notes
Andrew will work with group moving from contrib to provisional to migrate projects in svn
Peter will work on migrating contrib projects into JIRA's Sakai project
Chat/Chat2
there was a lot of debate about this. Sweeping changes that should have been discussed with the community first.
current Chat tool has a lot of problems
Linda will load test the tool during the QA cycle
Some want the old tool and what we've been calling chat2 available at the same time. Implementors will be able to choose between the two
Release Activity Scheduling
Branching the release: Will occur March 28th when we tag after QA release meeting
There are some components that have already branched (GB, chat).
Question asked- Anyone managing their own branches? A: Not really. Chris volunteered to manage OSP and Clay/BU to manage Mailtool.
Conversion Scipts
Folks are being very good at checking this kind of stuff in
ACTION ITEM: lance will ping dev list reminding them to add to this
Daily Countdown Meetings
Will hold these at 11am during last week of release cycle.