On Thu, Sep 17, 2020 at 06:49:19PM +0200, Kurt Roeckx wrote:
> - It doesn't go into 3.0. No idea what the best way to tag them
> is.
So I've created a "Post 3.0.0" milestone for that.
Kurt
I've found what's going wrong there, and I agree that it needs to be
fixed ASAP, although I don't view it per se as a beta 1 blocker.
Either way, a fix is coming up.
Cheers,
Richard
On Thu, 17 Sep 2020 19:21:50 +0200,
Dmitry Belyavsky wrote:
>
>
> Dear Matt,
>
> I think #12891 is a
On 18/09/2020 08:26, Richard Levitte wrote:
> On Thu, 17 Sep 2020 15:57:52 +0200,
> Tomas Mraz wrote:
>> I do not think the milestone should include nice-to-have items.
>
> Another view is that beta 1 is feature freeze. If those nice to have
> items are characterized as new features, then it
On Fri, 2020-09-18 at 09:26 +0200, Richard Levitte wrote:
> On Thu, 17 Sep 2020 15:57:52 +0200,
> Tomas Mraz wrote:
> > I do not think the milestone should include nice-to-have items.
>
> Another view is that beta 1 is feature freeze. If those nice to have
> items are characterized as new
On Thu, 17 Sep 2020 18:49:19 +0200,
Kurt Roeckx wrote:
>
> On Thu, Sep 17, 2020 at 01:48:18PM +0100, Matt Caswell wrote:
> > So - this leads me to the question - what is the milestone for? Does it
> > means these things *must* go in before we can release beta 1? Or does it
> > mean we would
Dear Matt,
I think #12891 is a significant problem. I'd suggest fixing it before beta1
or at least discuss it.
Many thanks!
On Thu, Sep 17, 2020 at 3:48 PM Matt Caswell wrote:
> There's been quite a number of PRs added to the 3.0 beta 1 milestone.
>
> Within the PRs there are a couple of bug
On Thu, 2020-09-17 at 13:48 +0100, Matt Caswell wrote:
> There's been quite a number of PRs added to the 3.0 beta 1 milestone.
>
> Within the PRs there are a couple of bug fixes:
>
> https://github.com/openssl/openssl/pull/12884
> https://github.com/openssl/openssl/pull/12874
>
> IMO these
