Page History

...

Edit all the pom.xmls <version> tags (done for 2.2.2)

Edit all the README.txt files (done for 2.2.2)

Edit all misc/version.properties (done for 2.2.2)

Grouper client

• conf/grouper.client*.properties (done for 2.2.2)

Look for other occurrences of grouper.client*.properties and refresh them (should only be grouper API) (done for 2.2.2)

Look for grouperClient.jar in SVN, and update it after build and copy to release server (should only be grouper API) (done for 2.2.2)

Grouper API

• GrouperVersion.java (done for 2.2.2)
• Make sure the subject jar up to date in api lib (done for 2.2.2)
• Run the command line utility to code generate which jars/sizes/etc are expected: GrouperCheckconfig.main() (done for 2.2.2)

Grouper installer

• grouper.installer.example.properties (done for 2.2.2)
• GiGrouperVersion.java (done for 2.2.2)

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.2.2)
• 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.2.2)
• Generate the wssec aar's and commit them (done for 2.2.2)
• Generate WSDLs and commit them (done for 2.2.2)

Search for the old version (e.g. 2.2.1 or 2_2_1 or 2_2_001) in all the files (done for 2.2.2)

Tag all (API, UI, WS, QS, client, etc) (done for 2.2.2)

• In git, the tag should be something like: GROUPER_1_2_12, tag for last commit in branch, and push tag (done for 2.2.2)

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.3.0)

...

See which config files / jar files / ddl changed since last release, make sure there are entries in the change log. (done for 2.2.2)

If its a minor release, change the release version policy page

...

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.(done for 2.2.2)

Copyright 2015 Internet2

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Make sure the subjects.sql and quickstart.xml file are in the release directory (copy from 2.2.1) (done for 2.2.2)

Misc Checks

• Make sure all tables, views, and cols (of tables and views) have comments in the DB (oracle or postgres). (dont do 2.2)
• 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.2.1)

...

...