Release postmortem

[Cantor, Scott]

Back from TechEx and I think Jenkins is green again for the moment. The breakage has been a mix of problems mostly stemming from not accounting for the project refactor's impact on the javadocs and it took most of last week to untangle.

Right now we have a mix of projects referencing the 17.0.2-SNAPSHOT parent to pick up a dependency change for a future patch in the IdP installer, and mostly everything locked back on 17.0.1.

Phil and I manually dealt with the javadocs and got them all re-built and posted to a new location under shibboleth.net/api/ and updated the wiki redirectors to reference those. Those are "only" the docs, not the Maven sites. I did not update the released sites. Many wiki links are still broken due to the changes to the libraries, that's just a long term cleanup task, it was a known issue.

I *think* that the javadoc:aggregate-jar goal should build the right doc artifacts going forward.

I did not yet deploy any V4 docs there but I'm inclined to do that for at least the latest ones.

Requests for SNAPSHOT docs to either the older location or the /api path are being rewritten to the Nexus location we deploy the sites to for now.

Next steps:

I think we should go ahead and unlock the parent POM in all the projects. We don't normally (*) but for now if we hold off on any dependency changes, that will let us verify that docs are still building properly, let us pull some extra properties from the POMs, and allow Tom to finish testing the signing of our snapshots.

Secondly, we have things set up to complete the migration away from building the Maven sites and working on how to deploy the aggregated docs. That will also be much easier with the parent unlocked.

Barring any objections, I'll unlock everything later today. I don't *think* we need to prematurely update all the inter-dependencies to X.0.1-SNAPSHOT, but that's partly what I want to verify (will do that locally).

-- Scott 

(*) Historically we left the projects locked to ensure that any dependency bumps were explicit in each project and to avoid the need to re-release every library to do an IdP patch. We discussed the issues with that last call without reaching any definite conclusions, particularly with plugins, but for now we're just doing cleanup on the POMs and the doc build, so that's not going to change anything we don't mean to.