Steps needed to make a Grouper release
Changes in SVN
Check git to make sure all commits in 2.2 are in master (DONE from Aug 2, 2015 - April 5, 2016)
Edit all the pom.xmls <version> tags (DONE for 2.3)
Edit all the README.txt files (DONE for 2.3)
Edit all misc/version.properties (DONE for 2.3)
Grouper client (DONE for 2.3)
- conf/grouper.client*.properties (DONE for 2.3)
Look for other occurrences of grouper.client*.properties and refresh them (should only be grouper API, wsSourceAdapter, subject) (DONE for 2.3)
Look for grouperClient.jar in SVN, and update it after build and copy to release server (should only be grouper API)
- GrouperVersion.java (DONE for 2.3)
- Make sure the subject jar up to date in api lib (DONE for 2.3)
- Run the command line utility to code generate which jars/sizes/etc are expected: GrouperCheckconfig.main() (DONE for 2.3)
Grouper installer (DONE for 2.3)
- grouper.installer.example.properties (DONE for 2.3)
- GiGrouperVersion.java (DONE for 2.3)
- 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 (DONE for 2.3)
- grouper-ws.base.properties (DONE for 2.3)
- 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.3)
- 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.3)
- Generate the wssec aar's and commit them (DONE for 2.3)
- Generate WSDLs and commit them (DONE for 2.3)
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.3)
Tag all (API, UI, WS, QS, client, etc) (DONE for 2.3)
- In git, the tag should be something like: GROUPER_1_2_12, tag for last commit in branch, and push tag (DONE for 2.3)
For a major release, do a branch for all (API, UI, WS, QS, client) as e.g. GROUPER_1_4_BRANCH (won't do until we start work on 2.4.0)
For the final build, replace all the pom.xml <version>x.y.z-SNAPSHOT</version> with the <version>x.y.z</version>, then tag, and then branch or change to <version>x.y.(z+1)-SNAPSHOT</version> (done for 2.3.0)
See which config files / jar files / ddl changed since last release, make sure there are entries in the change log.
If its a minor release, change the release version policy page (DONE for 2.3)
Handle Copyright According to Policy
Run the copyright wizard on the entire branch for java files. Or you can diff in version control and go through the new files. Note, only new files should have diffs... this is the custom copyright. You can update the year for new files, don't update the year for existing files. The year should be used and not a range. That is our policy on copyrights.
Make sure the subjects.sql and quickstart.xml file are in the release directory (copy from 2.3.0) (DONE for 2.3.0)
- Make sure all tables, views, and cols (of tables and views) have comments in the DB (oracle or postgres). (dont do 2.3.0)
- Make sure the grouper-ws web.xml file has the security basic auth in there (didn't get accidentally overridden in commit) (done for 2.3.0)
If possible run a security scan against a test instance - University of Pennsylvania via Chris? (dont do for 2.3.0)
*We have not carried out a thorough security review of the existing code base for any version of Grouper. We should do that in order for the incremental reviews to be adequate. (dont do for 2.3.0)
Run API (SuiteDefault) JUnit tests (set true in all JUnit test includes in grouper.properties). Also run the Grouper Installer, it should end in success for the client connecting to the WS and you should be able to use the UI.
API JUnit Tests
OS X (10.6)
Done by Chris
In progress by Chris
MySQL (with utf/bin collation table types)
Done by Shilen. All tests pass.
- MySQL windows
- MySQL unix with case sensitive table names
- () MsSQL (new)
Try the UI with a few different languages in the browser request (en without US, french, something not common)
Try checkConfig tests.
Upgrade from x.y-1 to x.y (e.g. 2.2 to 2.3).
- Install 2.2.2
- Download and run 2.2.2 installer
- Open the UI, browse around
- Upgrade to 2.3.0: https://spaces.at.internet2.edu/pages/viewpage.action?pageId=27230523
- Download 2.3.0
- Download 2.3.0 ui
- Configure grouper.hibernate.properties
- Upgrade the registry: C:\temp\grouperUpgrade\grouper.apiBinary-2.3.0\bin>gsh -registry -runscript
- Build the UI:
- copy build.properties.template to build.properties
- Edit the build.properties
- C:\temp\grouperUpgrade\grouper.ui-2.3.0>ant dist
- Map /grouper in tomcat: C:\temp\grouperUpgrade\grouper.ui-2.3.0\dist\grouper
- Open the UI, browse around
Install the grouper installer
- Download grouper installer
- Run: java -jar grouperInstaller.jar
- Try the UI that was installed
- Make sure gsh.sh and gsh works in api, ws, ui for 2.3.0
OS X (10.6)
DONE for 2.3 (chris)
Web Service JUnit Tests (Grouper WS and Grouper Client) (DONE for 2.3.0, though 9 errors in client tests)
WS samples (DONE for 2.3.0) (note: still need to code/run new SOAP samples)
WS javadoc (generate, commit, test). Make sure new operations / args / etc are documented in the WS doc page (TODO?)
UI internationalization tests (TODO?)
Test an API patch
Compile test on server
Packaging and releasing
- ssh to i2mibuild.internet2.edu (DONE for 2.3.0)
- cd to ~mchyzer (DONE for 2.3.0)
- Build all with: [mchyzer@i2mibuild mchyzer]$ bin/buildGrouperAll.sh GROUPER_x_y_z (DONE for 2.3.0)
- This is the same as these individual commands:
- bin/buildGrouper.sh GROUPER_x_y_z
- bin/buildGrouperWs.sh GROUPER_x_y_z
- bin/buildGrouperClient.sh GROUPER_x_y_z
- bin/buildGrouperUi.sh GROUPER_x_y_z
- bin/buildGrouperQs.sh GROUPER_x_y_z
- Note: sometimes the grouperWs doesnt build correctly due to a bug with javadoc, just try building the ws again...
Resulting .tar.gz's are in ~mchyzer/tmp/grouperAll/build_<username>. There are both source and binary tarballs for the API and Client packages.
- scp packages built above, to: (DONE for 2.3.0)
- Build to demo server, after the release is tagged, and built on the build server in Chris' directory... (TODO after release)
- Ask email@example.com to change the nagios URL... e.g. https://grouperdemo.internet2.edu/status_grouper_v2_4/status?diagnosticType=all
[appadmin@i2midev1 2.0.0]$ pwd
[appadmin@i2midev1 2.0.0]$ ./upgrade_2.0.0.sh
Packaging and releasing : provisioning
After tagging, publish to maven central by following the instructions on v2.1.0 Grouper Development Environment Using Maven. (DONE for 2.3.0)
grouper.psp-version.tar.gz to the release URL. (DONE for 2.3.0)
Archive the current release
- Create PDF of current documentation for the release archive
- Browse -> Advanced -> Export Space
- select PDF, uncheck save comments, clear all
- select pages to export. try to omit non-product pages, defunct pages, and pages for future releases.
- export, save to desktop, rename and attach to GrouperWG/Archives
- update Archives page with info from the current vN.N+Release+Notes page and links from the Software+Download page.
Update vN.N+Release+Notes page
Generally roll notes from the oldest release off and add notes for the new release. Keep previous release notes in there, so that we always have current + previous.
Update Software+Download page
- Make sure you have copied this to the archives page per above
- freshen links and rows in software download table
- freshen cvs info at bottom of page
- update release date
Review product pages
- Ensure that each page identifies which version it's current for, as in "Building the Grouper API as of v1.4.1" as an h2 at the top.
- Review incoming and outgoing links info for each page.
- If there's new features with new pages, update the Grouper+Product page to appropriately reference the new pages.
- Is it all there?
- Are there pages in the Working Group or Community areas that have graduated to being core product doc? Negotiate with originator to move them over to the product pages.
Just update the "NEW!!" message on this page. Maybe review the Background section to see if it could use some freshening. Maybe add a news item
Review Training Videos
- Determine which Grouper training videos need to be updated. Are new training videos required?
Update Grouper Wiki Documentation
- ***** IMPORTANT: For Grouper 2.2 see the Documentation TO DO's page.
- Update the Grouper Downloads page
- Update the spec sheet
- Update wiki pages for all changed features.
- Review the Glossary, remembering this could be a first place new people go to learn important terms. It seems rusty to Emily but not exactly sure how to improve it. HELP appreciated.
- Be sure that wiki pages on new Features are linked correctly from the Admin Guides TOC page
Release Numbering and Testing Period
As of Feb. 2012, these procedures were adopted regarding release numbering and testing:
- The X.X.0 release will be considered a pre-release, like a Release Candidate
- That will be the testing release
- The X.X.1 release will be the actual release, presumably after any initial bugs identified have been fixed.
Notify about the release
- Compose email to grouper-dev and grouper-users with highlights of the new release and link to the Grouper Downloads page
- email to mw-announce [at] internet2.edu email list
- Highlights should resemble those on the vN.N Release Notes page and maybe even be identical.
- If it's especially enlightening, also include a direct link to the changelog (vN.N+Release+Notes#vN.NReleaseNotes-changelog) or to an appropriate Jira report.
- Change jira admin to make that version released, and if the next build or version isnt there, add it
- update Grouper website features page to highlight newest Grouper features
- Social Media: Announce the new Grouper release on the InCommon and Internet2 Facebook and Twitter accounts as appropriate
- work with Todd Sedmak, Internet2 PR & Media Relations Manager, around other possible publicity/press releases etc.
- A Grouper Team member (DaveL for the Grouper 2.2 release) will create a Youtube video (using same tools as the Grouper Training videos) highlighting new features
- promote this video in coordination with the Internet2 Marketing and Communications Team
- schedule a webinar to promote the new release