Re: [openssl-project] Anything else to go in before I call the freeze?

2018-03-19 Thread Bernd Edlinger
OK, I freezed the repository for you. On 03/19/18 19:25, Matt Caswell wrote: > Please can someone freeze the repo for me: > > $ ssh openssl-...@git.openssl.org freeze openssl matt > > I will still take #5677 "Fix no-sm3 (and no-sm2)" after the freeze. Also > if anyone can come up with a fix for

Re: [openssl-project] Anything else to go in before I call the freeze?

2018-03-19 Thread Matt Caswell
Please can someone freeze the repo for me: $ ssh openssl-...@git.openssl.org freeze openssl matt I will still take #5677 "Fix no-sm3 (and no-sm2)" after the freeze. Also if anyone can come up with a fix for the failing master in Travis that would be good. Matt On 19/03/18 16:48, Matt Caswell

Re: [openssl-project] Anything else to go in before I call the freeze?

2018-03-19 Thread Richard Levitte
In message <1ab966c8-02d4-cf1f-504a-a54999a7c...@openssl.org> on Mon, 19 Mar 2018 16:33:57 +, Matt Caswell said: matt> Let me know asap... #5662 #5663 -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/

Re: [openssl-project] Anything else to go in before I call the freeze?

2018-03-19 Thread Matt Caswell
BTW please review #5673. I'd like a clean run from run-checker for the release tomorrow. Matt On 19/03/18 16:33, Matt Caswell wrote: > Let me know asap... > > > Matt > ___ > openssl-project mailing list > openssl-project@openssl.org >

[openssl-project] Anything else to go in before I call the freeze?

2018-03-19 Thread Matt Caswell
Let me know asap... Matt ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Richard Levitte
In message <97cff4a5-de0e-4d17-8a07-242961d6f...@akamai.com> on Mon, 19 Mar 2018 12:47:05 +, "Salz, Rich" said: rsalz> Yes, SM2 ECC is a big one that seems to have fallen thru the cracks. And 4848. That is *very* unfortunate. rsalz> rsalz> Instead time and energy went to

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Salz, Rich
Yes, SM2 ECC is a big one that seems to have fallen thru the cracks. And 4848. That is *very* unfortunate. Instead time and energy went to FIXING Android, configure command-line, and various no-XXX builds. ___ openssl-project mailing list

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Richard Levitte
In message <001364a7-e3c5-4e2b-8f0b-6ed1a041f...@akamai.com> on Mon, 19 Mar 2018 12:27:19 +, "Salz, Rich" said: rsalz> I would consider it a bug-fix FWIW. rsalz> rsalz> I thought we extended the deadline so that we could review more rsalz> third-party PR's.I'm still

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Tim Hudson
I too see this in the "bug fix" area - although you can make a reasonable counter argument (but I don't see a lot of point in doing so). Improving the build environment is a good thing IMHO ... Tim. On Mon, Mar 19, 2018 at 10:27 PM, Salz, Rich wrote: > I would consider it a

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Richard Levitte
Ok. I see it the same way, and indications are that others would agree as well... In message on Mon, 19 Mar 2018 11:56:23 +, Matt Caswell said: matt> This is definitely in the grey area, but I tend to think it is more

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Matt Caswell
This is definitely in the grey area, but I tend to think it is more towards the "fix" side than the "feature" side. Also the risk is significantly mitigated by it only impacting VMS. Matt On 19/03/18 11:52, Richard Levitte wrote: > In message <7aa44215-febf-73d2-3d0f-12f99b44b...@openssl.org>

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Richard Levitte
In message <7aa44215-febf-73d2-3d0f-12f99b44b...@openssl.org> on Mon, 19 Mar 2018 11:14:27 +, Matt Caswell said: matt> matt> matt> On 19/03/18 10:58, Richard Levitte wrote: matt> > Andy has indicated that the rather special construction to get command line C macro

[openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Dr. Matthias St. Pierre
Hi, in view of the upcoming beta release and the release strategy (see below) it is a little bit disturbing that our GitHub milestone for 1.1.1 shows only 30% completion. How are we going to deal with this? Shouldn't the PR's and issues be examined

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Matt Caswell
On 19/03/18 08:27, Dr. Matthias St. Pierre wrote: > Hi, > > in view of the upcoming beta release and the release strategy (see > below) it is a little bit disturbing that our GitHub milestone for 1.1.1 > shows only 30% > completion. How are we

[openssl-project] Code freeze later today

2018-03-19 Thread Matt Caswell
Just a reminder that beta1 is scheduled for release tomorrow so, in preparation for that, I will be freezing the repo later today. Of course this really means feature freeze as well since this will be your last opportunity to push features before the beta release. So if there is anything still

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Richard Levitte
Andy has indicated that the rather special construction to get command line C macro definitions and include paths specs collected in one place (*) is perhaps too special and could be handle by parsing CPPFLAGS and extra multiple definitions to get them collected in one spot. I have some ideas

Re: [openssl-project] GitHub milestone for 1.1.1

2018-03-19 Thread Matt Caswell
On 19/03/18 10:58, Richard Levitte wrote: > Andy has indicated that the rather special construction to get command line C > macro definitions and include paths specs collected in one place (*) is > perhaps too special and could be handle by parsing CPPFLAGS and extra > multiple definitions to