Thanks for all of your hard work on this, much appreciated! A little feedback for 3.5.1 (not helping with 3.5.0): checksums for the binaries too, not just the source.
That's it. :-) On 8 April 2017 at 09:05, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > 24. Publish the website with https://cms.apache.org/maven/publish > 25. Send the announcement email > 26. (PMC only) Record the release on > https://reporter.apache.org/addrelease.html?maven > 27. Tweet the release > > TODO: > 28. Wait for the announcement email to show up on the > https://mail-archives.apache.org/mod_mbox/maven-announce/ archives > 29. Update the site history with the announce email > 30. Publish the site again > 31. Celebrate!!! > > On 7 April 2017 at 09:59, Stephen Connolly <stephen.alan.connolly@gmail. > com> > wrote: > > > 23. Mark the version in JIRA as released > > > > On 7 April 2017 at 09:40, Stephen Connolly <stephen.alan.connolly@gmail. > > com> wrote: > > > >> 14. Close the vote > >> 15. Commit the finalized release notes > >> 16. Commit the updated doap > >> 17. Add the release to the dist > >> > >> $ cd ~/tmp > >> $ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 > maven-dist > >> $ cd maven-dist > >> $ mkdir -p 3.5.0/{binaries,source} > >> $ for ext in tar.gz zip ; do ( cd 3.5.0/binaries/ ; for hash in "" .asc > >> .md5 .sha1 ; do curl -O https://repository.apache.org/ > >> content/repositories/maven-1326/org/apache/maven/apache-mave > >> n/3.5.0/apache-maven-3.5.0-bin.$ext$hash ; done ) done > >> $ for ext in tar.gz zip ; do ( cd 3.5.0/source/ ; for hash in "" .asc > >> .md5 .sha1 ; do curl -O https://repository.apache.org/ > >> content/repositories/maven-1326/org/apache/maven/apache-mave > >> n/3.5.0/apache-maven-3.5.0-src.$ext$hash ; done ) done > >> $ svn add 3.5.0 > >> $ svn ci -m "Staging the binaries for the release" > >> > >> 18. Release the staging repo in nexus > >> 19. Release the binaries > >> > >> $ svn mv https://dist.apache.org/repos/dist/dev/maven/maven-3/3.5.0 > >> https://dist.apache.org/repos/dist/release/maven/maven-3 -m "Release > >> 3.5.0" > >> > >> 20. Deploy the current reference > >> > >> $ svn cp https://svn.apache.org/repos/infra/websites/production/maven > >> /components/ref/3-LATEST https://svn.apache.org/repos/i > >> nfra/websites/production/maven/components/ref/3.5.0 -m "Deploy the > 3.5.0 > >> reference documentation" > >> > >> 21. Draft the Announcement email > >> > >> 22. Wait for the binaries to sync to the mirrors (check > >> https://www.apache.org/mirrors/ look at the mean / median mirror age, > >> wait that long) > >> > >> On 4 April 2017 at 07:40, Stephen Connolly > <stephen.alan.connolly@gmail.c > >> om> wrote: > >> > >>> 12. Run the integration tests: (in debian as that matches the ci > server) > >>> > >>> $ ID=$(docker build environments/debian-jdk7) && > >>> docker run -it --rm -v $(pwd):/root/maven-integration-testing -v > >>> $(pwd)/../maven:/root/maven $ID bash > >>> $ cd /root > >>> $ mvn clean install -Prun-its -Dmaven.repo.local=$HOME/tmp/repo > >>> -DmavenDistro=../maven/target/checkout/apache-maven/target/a > >>> pache-maven-3.5.0-bin.zip > >>> > >>> 13. Publish the integration tests site: (by bind mounting the test run > >>> we can publish the results from inside docker outside of docker) > >>> > >>> $ mvn -Preporting site site:stage && mvn scm-publish:publish-scm > >>> > >>> On 3 April 2017 at 23:36, Stephen Connolly < > >>> stephen.alan.conno...@gmail.com> wrote: > >>> > >>>> 11. Run the source release analyzer (https://github.com/stephenc/s > >>>> ource-release-validator/commit/2e91ac959d0320a509e023b11b6389 > cc05719cdb) > >>>> and reply to the vote with the results. > >>>> > >>>> On 3 April 2017 at 23:18, Stephen Connolly < > >>>> stephen.alan.conno...@gmail.com> wrote: > >>>> > >>>>> Note to self, here's all the steps so far > >>>>> > >>>>> 1. $ export JAVA_HOME=jdk7 > >>>>> 2. $ export PATH=${JAVA_HOME}/bin:${PATH} > >>>>> 3. $ mvn release:prepare release:perform > >>>>> 4. $ cd target/checkout > >>>>> 5. $ export MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=512m > >>>>> 6. Close staging repo > >>>>> 7. $ mvn -Preporting site site:stage > >>>>> 8. $ mvn scm-publish:publish-scm > >>>>> 9. Send vote email > >>>>> 10. Start preparing the release notes > >>>>> > >>>> > >>>> > >>> > >> > > >
