Release maven IdP distribution enforcer data repository 1.0.5
Basics
Logistics
Basics
Logistics
Description
Environment
None
Activity
Philip Smart April 14, 2022 at 2:32 PM
Philip Smart
April 14, 2022 at 2:32 PM
Versions look good. Parent looks good.
Rod Widdowson April 14, 2022 at 2:29 PM
Rod Widdowson
April 14, 2022 at 2:29 PM
Assigbning to Phil to check my working.
I have updated the parent project to point to 1.0.6 of mvn-data
Rod Widdowson April 14, 2022 at 2:28 PM
Rod Widdowson
April 14, 2022 at 2:28 PM
# for interactive passphrase entry (maybe not required for others)
export GPG_TTY=$(tty)
# somewhere to store a tmp maven repo
export REPO=/tmp/rodsrepo
cd /tmp
git clone git@git.shibboleth.net:java-mvn-enforcer-data
cd java-mvn-enforcer-data
git checkout main
mvn -Dmaven.repo.local=$REPO -Prelease clean verify
mvn -Dmaven.repo.local=$REPO -DgenerateBackupPoms=false -DnewVersion=1.0.6 versions:set
# Edit pom.xml, bump dependency versions to release
# vi pom.xml
# Be sure there are not SNAPSHOT deps in any pom (from base dir).
git status
find . -name 'pom.xml' -exec grep SNAPSHOT {} \;
# If the output contains SNAPSHOTs change to release
mvn -Dmaven.repo.local=$REPO -Prelease clean verify
git add -A
git commit -m 'Update files to be tagged for release'
git tag -s -m 'Tag 1.0.6 release' 1.0.6
mvn -Dmaven.repo.local=$REPO -DgenerateBackupPoms=false -DnewVersion=1.0.7-SNAPSHOT versions:set
# Be sure there are SNAPSHOTs in the right places.
find . -name 'pom.xml' -exec grep SNAPSHOT {} \;
git add -A
git commit -m 'Bump version after release'
git checkout 1.0.6
mvn -Dmaven.repo.local=$REPO -Prelease,sign clean verify
## commit the work
ssh -L 1581:127.0.0.1:1581 -N build.shibboleth.net -f
mvn -Dmaven.repo.local=$REPO -DskipTests -DdeployAtEnd=true -Prelease,sign deploy
git checkout main
git push origin main
git push origin 1.0.6
Rod Widdowson April 14, 2022 at 1:43 PM
Rod Widdowson
April 14, 2022 at 1:43 PM
Turns out I did the entire release without the critical change.
Rod Widdowson April 12, 2022 at 2:28 PM
Rod Widdowson
April 12, 2022 at 2:28 PM
All done
Completed
Details
Details
Assignee
Philip Smart
Philip SmartReporter
Rod Widdowson
Rod WiddowsonCreated April 9, 2022 at 12:52 PM
Updated April 17, 2022 at 1:51 PM
Resolved April 17, 2022 at 1:51 PM
Sigh
We need to be sure that we are (finally) ready for 4.2.
In case subsystems get build by non standard people we need to make sure that the key rings for the
net.shibboleth.*
andorg.opensaml.*
groups contain all the developers' signatures. Our usual procedure is to only add keys we have seen, but for our own projects it makes sense to be general. After all trust is not an issue.We need to make sure that the new BC artifacts (as per https://shibboleth.atlassian.net/browse/JPAR-205) and the transitive closure of its dependencies are OK for signatures.
And because these keys will be used to test a real release these must be bundled into a release.