Child pages
  • Grouper Call 9-Dec-09_

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Tom Barton, U. Chicago  (Chair)
Gary Brown, Bristol
Lynn Garrison, The Pennsylvania State University
Shilen Patel, Duke
Chris Hyzer, U. Penn
Tom Zeller, U. Memphis
Steve Olshansky, Internet2
Emily Eisbruch, Internet2 (scribe)

*New Action Items*

Wiki Markup\[GrouperWG:AI\] (Gary) will add a link in the release process checklist for security issues and mention that U. Penn can do scanning for future releases. \
[GrouperWG:AI\] (Chris) will start researching integration of Grouper with KIM workflows \
[GrouperWG:AI\] (TomB) will talk with USC, UBC, UW and U. Arizona about testing Grouper KIM integration. \
[GrouperWG:AI\] (Emily and SteveO) will confer on presenting the Grouper Q&A audio file on the Grouper website.

 *Carry Over Action Items*

Wiki Markup\[GrouperWG:AI \ ] (Everyone) update the upgrade change log wiki page as needed re jars and config files, and upgrade instructions.[https://spaces.at.internet2.edu/display/GrouperWG/Grouper+change+log+v1.5] \
[GrouperWG:AI\] (Tom) will create Release Notes.  \
 [GrouperWG:AI\] (SteveO) will update website and wiki as needed for the Grouper 1.5.0 release.

*Grouper 1.5 Release Final Coordination*

Wiki MarkupThe code has been frozen for the release of Grouper 1.5.0. TomB and SteveO will handle final steps, including creating release notes, archiving the Grouper 1.4.2 wiki pages, migrating the new Grouper 1.5.0 wiki pages into the regular/default pages, etc. \
[GrouperWG:AI\] (Emily and SteveO) will confer on presenting the Grouper Q&A audio file on the Grouper website.
Goal is to have the release ready on Friday, 11-Dec-09.

*Test and Release Process Review*

...

Chris said that U. Penn could do scanning to check for security issues as part of future releases.

Wiki Markup \ [GrouperWG:AI\] (Gary) will add a link in the release process checklist for security issues and mention that U. Penn can do scanning for future releases.

Testing different databases is useful. Is there a way to automate that testing? It could be helpful if Internet2 had a VM that could be used for testing Grouper with different databases at code freeze time, though there could be issues in keeping all the databases updated.  Is it practical to test all databases with all settings? While testing the Grouper 1.5.0 release, Chris got a new computer and reinstalled MySQL with different settings, causing some issues.
Oracle is available to be tested in-house by some of the developers. TomZ can test Postgress, which is used in production at U. Memphis.

...

Chris, noted that in light of the way KIM handles workflows with responsibilities, there is more integration work needed before Grouper can be used with KIM workflows. Chris will delve into this issue when the current group integration is complete.  A central question is whether it's possible to add a group to a responsibility. Other institutions besides Penn State are also interested in this workflow question.unmigrated-wiki-markup

\[GrouperWG:AI\] (Chris) will start researching integration of Grouper with KIM workflows

Q: Where does the Grouper/KIM integration work go (proof of concept connector, & documentation)?
A: Chris: It will go in the Grouper CVS. Could go in the KIM subversion also.  Documentation will go on Grouper and KIM wikis, with pointers.

We will need campuses to test it and provide feedback.   Campuses already running Grouper in production would need to try the Grouper KIM integration in a proof-of-concept environment, until changes are committed in the head branch.

Wiki Markup\[GrouperWG:AI\] (TomB) will talk with USC, UBC, UW and U. Arizona about testing Grouper KIM integration.

*Branches*

Where should changes get committed?https://mail.internet2.edu/wws/arc/grouper-dev/2009-12/msg00006.html
- GROUPER_1_5_BRANCH is for bug fixes.
- HEAD is for short-term functionality fixes, and where Chris is working on the Grouper and KIM integration.
The 1.6 will be the next released version with enhancements, including Grouper KIM integration.
Then there will be a 2.0 version after 1.6.
Gary suggests waiting until we get Subversion before we start additional branching.

...