<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Concerning PR #4930:</p>
<p>Originally that PR was about extending support for PKCS#12 input
in apps, which meanwhile has been superseded mostly by OSSL_STORE.<br>
I meanwhile carved out the most interesting remaining pieces of
the PR and contributed them separately.<br>
I've just rebased and cleaned up the various remaining commits.</p>
<p>
What is still left are fixes for several corner cases in PKCS#12
input and its error handling.<br>
There are also some rather unrelated fixes to several apps and
their documentation, which I could separate if requested.<br>
I don't think any of this is critical before the beta release; in
particular there are no feature or API changes any more.</p>
<p> David<br>
</p>
<div class="moz-cite-prefix">On 14.09.20 19:32, Richard Levitte
wrote:<br>
</div>
<blockquote type="cite" cite="mid:874ko0s1qq.wl-levitte@openssl.org">
<pre class="moz-quote-pre" wrap="">On Sun, 13 Sep 2020 22:41:23 +0200,
Dr. Matthias St. Pierre wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Conversely, there were also pull requests associated with the '3.0.0' or '3.0.0 beta1' milestone,
without being associated to the '3.0 New Core + FIPS' project. This has been fixed now.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I fail to see why the milestones '3.0.0' / '3.0.0 beta1' must be 1:1
with the '3.0 New Core + FIPS' project. If we make them the same,
what's the reason to have both?
I just looked in the project, and these are issues and PRs the
presence of which I think is questionable:
#10612
#4930
#12860
#11311
Maybe there's a misunderstand of what "3.0 New Core" means. Please
note the lack of comma. But if that doesn't help, how about the
project description?
I've seen a bit too much of wanting to pile *everything* into that
project. That was never the intention.
Cheers,
Richard
</pre>
</blockquote>
</body>
</html>