Subject: Grouper Developers Forum
[grouper-dev] Draft Minuntes: Grouper Call of June 4, 2014
- From: Emily Eisbruch <>
- To: "" <>
- Subject: [grouper-dev] Draft Minuntes: Grouper Call of June 4, 2014
- Date: Mon, 16 Jun 2014 17:11:05 +0000
- Accept-language: en-US
Draft Minuntes: Grouper Call of June 4, 2014
Tom Barton, University of Chicago (Chair)
New Action items
[AI] (Tom) will reach out to another CIC School to see if they can help with testing.
Carry Over Action items
[AI] (Gail) will assist with testing the new Grouper UI (Gail has started this)
[AI] (Gail) will assist with Unit Testing Grouper 2.2 using Oracle Database
[AI] (Emily) share a publicity plan for Grouper 2.2 release with the core team
[AI] (Shilen) create a Grouper training video on the new Grouper UI
[AI] (Jim) make the University of Washington group events AD updating code available on GitHub and document its availability on the Community Contributions page. (DONE)
[AI) (DaveL) look at PSP ChangeLogDataConnector Inconsistency issue
[AI] (Shilen) investigate ways to get new attribtues in a single step (after 2.2 release)
Documentation Action Items
Reminder: check if updates are needed to the corresponding Grouper Training video
Release Steps for Grouper 2.2
Many items are marked done for 2.2.0.
Chris will handle the branch process when the release is ready.
Chris will look at the copyright wizard for this release and be sure it works correctly.
Testing Grouper 2.2:
-Chris will test using MySQL
-Gail will test using Oracle
-Jim will test using PostgreSQL
-Dave will test using MS SQL
How far back to go (to which back versions) in documenting the upgrade?
Would be helpful to look at upgrading from
Grouper 2.0 to 2.2
Grouper 2.1 to 2.2
What about sites still using Grouper 1.6?
Those sites should first upgrade from Grouper 1.6 to 2.1.
Then upgrade to from Grouper 1.1 to Grouper 2.2
-This should be noted on the upgrade page
Jim: University of Washington is doing an upgrade of one of their databased from PostgreSQL to MySQL.
Jim will provide notes on lessons learned from that. (There are some issues with null fields)
Chris suggests this approach for testing:
-First upgrade the data
-Run the UI or web services to be sure it works (browse the UI)
-Run API unit tests in a different schema
-Run Web Service tests for extra credit
API unit tests are sensitive to the underlying database
Best to do an install, check the API unit test, then do the upgrade in a separate place
Do we need to run unit tests on Oracle?
Shilen did it and it worked.
Chris: It is useful to run the unit tests on an upgrade to test that the DDL was set up correctly.
Protocols to follow
-Set up a blank Grouper 2.1, and upgrade it, and run the unit tests on that
-Start from scratch on Grouper 2.2 and run API unit tests on that
-If you have a database that's full, upgrade that to Grouper 2.2 and do sanity checks.
Chris has uploaded the tarball so unit testing can begin
Q: How do we manage versions of documentation?
A: When we change a feature, we indicate the version it's for.
This way all the docs can remain unified, rather than having separate doc sets for different Grouper versions)
Chris will work on the Release Notes page for Grouper 2.2 release
Emily will review the Software Downloads page at
Emily will update the wiki main page and Grouper website to reflect the new release
-Gail hopes to be able to test at end of the week of June 9
Is there a site using SQL server?
Chris: there is an Express Edition you can run on a PC (does not run on a MAC)
[AI] (Tom) will reach out to University of Iowa to see if they can help with testing.
Chris will email the Grouper-dev list to ask if there are sites that would want to look at the Grouper 2.2 release candidate. (DONE)
Target release date for Grouper 2.2. Is Friday, June 20, 2014
Next Grouper-Dev call: Wed. June 18 at noon ET
Emily Eisbruch, Technology Transfer Analyst
office: +1-734-352-4996 | mobile +1-734-730-5749
- [grouper-dev] Draft Minuntes: Grouper Call of June 4, 2014, Emily Eisbruch, 06/16/2014
Archive powered by MHonArc 2.6.16.