RE: Release done
The problem was running "make relupd" in the web worktree. It assumes CHANGES and NEWS in all branches. We could have discovered this earlier... "Dr. Matthias St. Pierre" skrev: (17 mars 2020 19:53:12 CET) >> Problems were due to: >> ... >> - Rename of CHANGES/NEWS to CHANGES.md/NEWS.md > >Strange what exactly was your problem? > >I anticipated this problem on the weekend and checked the release >scripts. >After some investigation, I came to the conclusion that it wouldn't be >a problem >for the OpenSSL_1_1_1-stable branch yet, because the markdown revamping >happened only on master. What did I miss? > >Matthias > > >P.S.: As a byproduct of my investigations I created >https://github.com/openssl/tools/pull/64 -- Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.
RE: Release done
Unfortunately, the server side hooks are not published anywhere. So I was not able to figure out that there might be a problem. I should have given you a heads-up nevertheless, sorry for the omission. Matthias > -Original Message- > From: Matt Caswell > Sent: Tuesday, March 17, 2020 8:29 PM > To: Dr. Matthias St. Pierre ; > openssl-project@openssl.org > Subject: Re: Release done > > > > On 17/03/2020 18:53, Dr. Matthias St. Pierre wrote: > >> Problems were due to: > >> ... > >> - Rename of CHANGES/NEWS to CHANGES.md/NEWS.md > > > > Strange what exactly was your problem? > > The website is supposed to update itself automatically when we push > stuff, so things like release notes etc get automatically generated. > From tools/release/README.md: > > Verify that the release notes, which are built from the CHANGES file > in the release, have been updated. This is done automatically by the > commit-hook, but if you see a problem, try the following steps: > > cd /var/www/openssl > sudo -u openssl -H make relupd > sudo -u openssl ./bin/purge-one-hour > > This didn't happen unfortunately. When I ran "make relupd" manually I got: > > make: *** No rule to make target > '/var/cache/openssl/checkouts/openssl/CHANGES', needed by > 'news/changelog.txt'. Stop. > > That particular make target is related to the *master* CHANGES file > (there are similar targets I think for other branches). > > Matt
Re: Release done
On 17/03/2020 18:53, Dr. Matthias St. Pierre wrote: >> Problems were due to: >> ... >> - Rename of CHANGES/NEWS to CHANGES.md/NEWS.md > > Strange what exactly was your problem? The website is supposed to update itself automatically when we push stuff, so things like release notes etc get automatically generated. >From tools/release/README.md: Verify that the release notes, which are built from the CHANGES file in the release, have been updated. This is done automatically by the commit-hook, but if you see a problem, try the following steps: cd /var/www/openssl sudo -u openssl -H make relupd sudo -u openssl ./bin/purge-one-hour This didn't happen unfortunately. When I ran "make relupd" manually I got: make: *** No rule to make target '/var/cache/openssl/checkouts/openssl/CHANGES', needed by 'news/changelog.txt'. Stop. That particular make target is related to the *master* CHANGES file (there are similar targets I think for other branches). Matt
RE: Release done
> Problems were due to: > ... > - Rename of CHANGES/NEWS to CHANGES.md/NEWS.md Strange what exactly was your problem? I anticipated this problem on the weekend and checked the release scripts. After some investigation, I came to the conclusion that it wouldn't be a problem for the OpenSSL_1_1_1-stable branch yet, because the markdown revamping happened only on master. What did I miss? Matthias P.S.: As a byproduct of my investigations I created https://github.com/openssl/tools/pull/64
Release done
The release is complete and the repo is unfrozen. Thanks to Paul Yang for doing the release reviewer role. Loads of problems this time. Looks like the release scripts need some adjustment. But through a combination of hacking and swearing at my computer it went through in the end. Problems were due to: - ongoing bug in dorelease.pl which doesn't move the old releases out the way properly - Rename of CHANGES/NEWS to CHANGES.md/NEWS.md - Bug in the script to update the source directory (doesn't seem to like us only having one active release) - Some problem (on our side) in the scripts related to purging the CDN cache. As a consequence I had to purge things "manually" as I found them, so there may be some pages that are un-purged (in particular I'm thinking the man pages). Matt
OpenSSL version 1.1.1e published
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenSSL version 1.1.1e released === OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.1.1e of our open source toolkit for SSL/TLS. For details of changes and known issues see the release notes at: https://www.openssl.org/news/openssl-1.1.1-notes.html OpenSSL 1.1.1e is available for download via HTTP and FTP from the following master locations (you can find the various FTP mirrors under https://www.openssl.org/source/mirror.html): * https://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-1.1.1e.tar.gz Size: 9792634 SHA1 checksum: e7105567d3e7e6353a0110f1adc81f69dbc8f732 SHA256 checksum: 694f61ac11cb51c9bf73f54e771ff6022b0327a43bbdfa1b2f19de1662a6dcbe The checksums were calculated using the following commands: openssl sha1 openssl-1.1.1e.tar.gz openssl sha256 openssl-1.1.1e.tar.gz Yours, The OpenSSL Project Team. -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhlersmDwVrHlGQg52cTSbQ5gRJEFAl5w3zsACgkQ2cTSbQ5g RJFdTQf+OeJkXlBCQvdJTv7ky6y7MGesCiMjcQsuFSLlWCHC6k2rNcgrZUH50vOB E6SH/VPvmreM+TNy95hP2uzGtFkpliIoZHu6NXJSo7QW9svBxzdqo8x7nYN3jhJ1 pEDjfk2vFz2Z/2uzoZdZVe4P8C4O4bFz79UmFUsXNffYcO0mDSih1jrjupASzSJH 0HB68p4lrdoJbiL6KIfGDLS5D+jn6KNU6gHT/6fhCalLQJ1StajpArrXXKrC2apP YAMTLYH5qxFReobKguOk6RwZnNI2Mdl75qWJ+Wu4PQORPryPeMJ00z82jx6Wv5zF vWQ4F8zoaiPfUSmyzOJgJQuRwrnNfg== =1uA3 -END PGP SIGNATURE-
