I would like to have it more prominent. I mean, yes, there should probably be a known issues page, but I think that whatever we do, we should have a line close to the one liking to the 1.1.0h tarball. Why send people chasing for it on other pages?
Also, some people are watching the source archive (https://ftp.openssl.org/) directly, so the more I think about it, the more it makes sense to me to place a patch there. openssl-1.1.0h-errata.patch ? That could easily be linked into the list of downloadable things in https://www.openssl.org/downloads/ with just a small tweak of the script we use to generate that list. In message <[email protected]> on Wed, 4 Apr 2018 09:38:26 +0100, Matt Caswell <[email protected]> said: matt> I'd say where we have introduced a regression in the latest release it matt> wouldn't hurt to have a "known issues" page, or similar, which links to matt> commits or other information about how to patch or work around an issue. matt> matt> I see no reason to make a new release unless we think the issue is matt> sufficiently serious and/or affects large numbers of users. matt> matt> Matt matt> matt> matt> On 04/04/18 09:32, Richard Levitte wrote: matt> > The attached report talks about CPP being required, but that's not the matt> > intention. Rather, this is an unnoticed mistake when cherry-picking matt> > from master to 1.1.0. matt> > matt> > The fix itself is easy (just add a line saying 'CPP=$(CC) -E'), and matt> > that's not what I'm here to talk about, but rather how we want to act matt> > in cases like this. Do we make a new release? Do we create an matt> > official patch? Do we make a link to the corrective github PR? matt> > My own sense is that we should put up something, and it should be matt> > visible on our download page and in our source archives. matt> > matt> > Whatever we decide should become policy. matt> > matt> > Cheers, matt> > Richard matt> > matt> > matt> > matt> > _______________________________________________ matt> > openssl-project mailing list matt> > [email protected] matt> > https://mta.openssl.org/mailman/listinfo/openssl-project matt> > matt> _______________________________________________ matt> openssl-project mailing list matt> [email protected] matt> https://mta.openssl.org/mailman/listinfo/openssl-project matt> _______________________________________________ openssl-project mailing list [email protected] https://mta.openssl.org/mailman/listinfo/openssl-project
