On 26/06/18 20:43, Salz, Rich wrote:
> That's interesting. Would we put a bugfix in 1.1.0, not put the fix in 1.1.1
> until our first "a" release?
>
> Or are you saying that if it's in 1.1.0, then we don't have to fix it until
> after 1.1.1 comes out? That seems justifiable to me.
The latte
On Tue, Jun 26, 2018 at 07:43:45PM +, Salz, Rich wrote:
> That's interesting. Would we put a bugfix in 1.1.0, not put the fix in 1.1.1
> until our first "a" release?
>
> Or are you saying that if it's in 1.1.0, then we don't have to fix it until
> after 1.1.1 comes out? That seems justifia
That's interesting. Would we put a bugfix in 1.1.0, not put the fix in 1.1.1
until our first "a" release?
Or are you saying that if it's in 1.1.0, then we don't have to fix it until
after 1.1.1 comes out? That seems justifiable to me.
On 6/26/18, 3:32 PM, "Matt Caswell" wrote:
On 26/06/18 18:18, Salz, Rich wrote:
> So are you saying look at the 73 open issues at
> https://github.com/openssl/openssl/milestone/9 and re-evaluate them?
Exactly. My guess is that a significant proportion of them also apply to
1.1.0 and therefore should not hold up the 1.1.1 release. At the
FYI
On 6/26/18, 2:45 PM, "Barry Fussell (bfussell)" wrote:
The evp_test is failing intermittently because there is an attempt to
malloc zero bytes when running the new test that came in with
this commit.
https://bitbucket-eng-rtp1.cisco.com/bitbucket/projects/TS/repos/cisc
So are you saying look at the 73 open issues at
https://github.com/openssl/openssl/milestone/9 and re-evaluate them?
On 6/26/18, 11:56 AM, "Matt Caswell" wrote:
I'm thinking that we should maybe re-asses the current milestones in github.
We currently use the following milestones
On Tue, Jun 26, 2018 at 04:56:26PM +0100, Matt Caswell wrote:
> I'm thinking that we should maybe re-asses the current milestones in github.
>
> We currently use the following milestones:
>
> Assessed - Anything against this milestone isn't relevant to the 1.1.1
> release (e.g. 1.0.2 specific iss
I'm thinking that we should maybe re-asses the current milestones in github.
We currently use the following milestones:
Assessed - Anything against this milestone isn't relevant to the 1.1.1
release (e.g. 1.0.2 specific issue)
1.1.1 - This is relevant to the 1.1.1 release but may not be specific
