...
- WS tests
- Look at jars not supposed to be there (from Chad)
- Once release ready: Tell packaging team to package it up
- Chris and Shilen upgrade
- This week
- Shilen (08/08/2018) - Tested upgrade using Oracle - Installed 2.3 API/UI/WS using installer with all patches. Upgraded each of the 3 components using the 2.4 installer without any issues.
- Shilen (08/08/2018) - Tested upgrade using Oracle - Installed 2.3 API using installer with only API patch 1. Upgraded API without any issues. Confirmed ehcache migration.
- Once release out: Chris to patch grouperClient checkconfig file size
- Chris and Emily to announce and update wiki
- Emily check wiki make sure things are up to date
- This week
...
Edit all the README.txt files (done for 2.4)
Edit all misc/version.properties (done for 2.4)
Update Grouper specsheet software requirements page (done for 2.4)
Grouper client (done for 2.4)
- conf/grouper.client*.properties grouperClient.webService.client.version = v2_4_000
Look for other occurrences of grouper.client*.properties and refresh them (should only be grouper API, wsSourceAdapter, subject) (done for 2.4)
Look for grouperClient.jar in SVN, and update it after build and copy to release server (should only be grouper API) (done for 2.4)
Grouper API
- GrouperVersion.java (done for 2.4)
Make sure the subject jar up to date in api lib- Run the command line utility to code generate which jars/sizes/etc are expected: GrouperCheckconfig.main() (did this but do it again in final version) (done for 2.4)
- Tag, build, get grouper client jar, but back in API, run GrouperCheckConfig, commit and push, tag again, build, and only take the API and put to release server (done for 2.4)
Grouper installer
- grouper.installer.example.properties (done for 2.4)
- GiGrouperVersion.java (done for 2.4)
Grouper UI
- translate the Grouper UI text to French (our French partners have agreed to do this, as of discussion with Chris in Fall 2012)
...
- grouper-ws.base.properties (done for 2.4)
- If there is a new minor version with changes to the wsdl, add a new source folder for that version, copy the coresoap *.javas over to it, refactor to change the package, change the build.xml to build a WSDL for that version. Change GrouperService to be like a previous version but add new methods or change methods in it (done for 2.4)
- Make sure that there is no coresoap (package) in use in src/grouper_ws_v1_6, src/grouper_ws_v2_0, etc. Take out all src/grouper_ws_vx_x except one, make sure they dont depend on each other (done for 2.4)
- Generate the wssec aar's and commit them (done for 2.4)
- Generate WSDLs and commit them (done for 2.4)
- Add src/grouper-ws_v2_4 to the source list of the Maven build-help plugin in grouper-ws/grouper-ws/pom.xml
Search for the old version (e.g. 2.2.2 or 2_2_2 or 2_2_002) in all the files (done for 2.4)
See which config files / jar files / ddl changed since last release, make sure there are entries in the change log. (do we do this anymore? Grouper changes v2.2)
If its a minor release, change the release version policy page (done for 2.4)
Make sure the crontab on webprod3 is installed for this version to make the "grouper.all*.tar.gz tarball" (done for 2.4)
Git Release Commit
This is the single commit that will be the official release. All code work should be finished at this point.
...
Make sure the subjects.sql and quickstart.xml file are in the release directory (copy from 2.3.0) (done for 2.4)
Misc Checks
- Make sure all tables, views, and cols (of tables and views) have comments in the DB (oracle or postgres). (TO DO on a rainy day)
- Make sure the grouper-ws and gruoper-ui web.xml file has the security basic auth in there (didn't get accidentally overridden in commit) (done for 2.4)
Security Review
Review UI / WS code changes* from the previous version with respect to Open Web Application Security Project (OWASP) top 10 web application security vulnerabilities
...