To elaborate on skipping 1.397 ..
The biggest advantage I see on using OSS Nexus for releasing Hudson is the ability to stage the release first. This gives an opportunity to test the staging before releasing it to maven central as explained here.
We have a test server setup to which the staged release is installed and any regressions are monitored actively. I'll let Geoff who leads the QA part of the release to explain more in details. Here is the gist of the setup
- The test server mimics some of the production servers with all the master-slave configuration
- Tier1 (~5) and Tier2 (~20) plugins are installed to make sure they all still work
(Geoff is going to add more test jobs and configuring them to include more of these plugins functionalities for further test spin of the plugins)
Installing and running the staged release in this test server and monitoring the jobs builds gives us added confidence in testing the fix of very elusive bugs like Remoting related bugs.
While we were releasing 1.397 the test server was being setup and we released it solely based on test-harness results. Fortunately the test server was commissioned on time to catch the issues and help us to pull back the 1.397 release quickly.
We allowed to run 1.398 on the test server for few days and released with added confidence.
[Hudson-Dev] Re: Hudson Build 1.398 is now available