SmartSite Release Planning v2.4.x
This is just an initial draft to keep track of tasks and changes
Brainstorming phase ...
- Replace the v2.4.x roster tool with the new one from Berkeley. I checked with Josh on this and there is some additional info in the sakai-dev mail archive under the "UC Berkeley's Roster tool" subject
- We will do this during phase two when 2.4.1 is available
- Are we gonna offer OPS in our 2.4.x environment? If not we can remove OSP.
- Convert any old provider ID data to new style one
- Add mothra ID to PersonInfo object
- DB update scripts going from v2.3.x to v2.4.x
- Chat migration to Chat2
- Increase providerId DB column from 1K to 4K
- DB links for stats tool
- Switch from using Kerberos Name to Mothra ID as the userEid
- Go through the DB tables and make sure that no KerberosNames are stored in any fields
- Update sakai userId/userEid mapping table. Update KerberosName to Mothra ID : SAK-639
- Check UI for any inappropriate userDisplayID. It should be UCD MailId and not MothraId
- Message center can be run as one to two tools, we need to decide on how we want to run it and prepare any associated conversion scripts
- DB UTF-8 conversion if not done before upgrade
- DB LONG/LONG RAW conversion if not done before upgrade
- We need to be able to import melete content that has been exported in sakai_2-3-x
- Banner maintenance windows coincides with SmartSite upgrade. We need to carefully coordinate this.
- Banner IP numbers will change
- Adjust DistAuth protection level 2 --> 3
See Also https://confluence.ucdavis.edu/confluence/x/tmg SmartSite Release Planning v2.4.x