Re: [openssl-project] Release strategy updates

2019-01-29 Thread Matt Caswell
On 14/01/2019 15:21, Matt Caswell wrote: > > > On 21/09/2018 14:19, Matt Caswell wrote: >> I am very concerned about stability of our API moving forwards. There >> are various discussions about changing the version number to 1.2.0 (or >> possibly 2.0.0) - which according to our versioning

Re: [openssl-project] Release strategy updates

2019-01-14 Thread Matt Caswell
On 21/09/2018 14:19, Matt Caswell wrote: > I am very concerned about stability of our API moving forwards. There > are various discussions about changing the version number to 1.2.0 (or > possibly 2.0.0) - which according to our versioning scheme would allow > breaking changes. Whilst this is

Re: [openssl-project] Release strategy updates & other policies

2018-09-28 Thread Tim Hudson
On Fri, Sep 28, 2018 at 4:55 PM Matt Caswell wrote: > Either we go with semver and totally commit to it - or we stick with what > we've already got. No > half-way, "well we're kind of doing semver, but not really". > +1 I see no point in changing what we are doing *without* getting the benefit

Re: [openssl-project] Release strategy updates & other policies

2018-09-28 Thread Matt Caswell
On 26/09/18 18:24, Viktor Dukhovni wrote: > > >> On Sep 25, 2018, at 9:51 AM, Matt Caswell wrote: >> >> 5.0.0 >> 5.0.1 (bug fix) >> 5.1.0 (add accessor) >> 6.0.0 (new feature) >> 6.0.1 (bug fix) >> 5.1.1 (bug fix)6.0.2 (bug fix) >> 5.2.1

Re: [openssl-project] Release strategy updates & other policies

2018-09-26 Thread Richard Levitte
In message <73e9cd06-575e-4cde-b137-95179b07b...@dukhovni.org> on Wed, 26 Sep 2018 13:24:11 -0400, Viktor Dukhovni said: > > > > On Sep 25, 2018, at 9:51 AM, Matt Caswell wrote: > > > > 5.0.0 > > 5.0.1 (bug fix) > > 5.1.0 (add accessor) > > 6.0.0 (new feature) > >

Re: [openssl-project] Release strategy updates & other policies

2018-09-26 Thread Viktor Dukhovni
> On Sep 25, 2018, at 9:51 AM, Matt Caswell wrote: > > 5.0.0 > 5.0.1 (bug fix) > 5.1.0 (add accessor) > 6.0.0 (new feature) > 6.0.1 (bug fix) > 5.1.1 (bug fix)6.0.2 (bug fix) > 5.2.1 (add accessor) > 6.1.0 (add

Re: [openssl-project] Release strategy updates & other policies

2018-09-26 Thread Kurt Roeckx
On Wed, Sep 26, 2018 at 07:06:18PM +0200, Richard Levitte wrote: > In message <20180926165825.ga14...@roeckx.be> on Wed, 26 Sep 2018 18:58:26 > +0200, Kurt Roeckx said: > > > On Tue, Sep 25, 2018 at 08:13:53PM +1000, Tim Hudson wrote: > > > On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell wrote: >

Re: [openssl-project] Release strategy updates & other policies

2018-09-26 Thread Richard Levitte
Speaking of this, I've started on a document that explores the meaning of changes and releases. Its objective is to create discussion and debate, and hopefully, we will eventually be able to create a working policy with sufficient detail.

Re: [openssl-project] Release strategy updates & other policies

2018-09-26 Thread Richard Levitte
In message <20180926165825.ga14...@roeckx.be> on Wed, 26 Sep 2018 18:58:26 +0200, Kurt Roeckx said: > On Tue, Sep 25, 2018 at 08:13:53PM +1000, Tim Hudson wrote: > > On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell wrote: > > > > > On 25/09/18 10:58, Tim Hudson wrote: > > > > On Tue, Sep 25, 2018

Re: [openssl-project] Release strategy updates & other policies

2018-09-26 Thread Kurt Roeckx
On Tue, Sep 25, 2018 at 08:13:53PM +1000, Tim Hudson wrote: > On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell wrote: > > > On 25/09/18 10:58, Tim Hudson wrote: > > > On Tue, Sep 25, 2018 at 7:23 PM Richard Levitte > > > wrote: > > > > > > So what you suggest (and

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 14:30, Richard Levitte wrote: > In message on Tue, 25 Sep > 2018 14:15:32 +0100, Matt Caswell said: > >> On 25/09/18 14:09, Tim Hudson wrote: >>> It would also mean our LTS releases are MAJOR.MINOR - as the PATCH is >>> the fixes we will apply - so it isn't part of the LTS

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 14:21, Richard Levitte wrote: > In message on Tue, 25 Sep > 2018 14:11:11 +0100, Matt Caswell said: > >> >> >> On 25/09/18 13:54, Richard Levitte wrote: >>> In message <896ece72-8923-801e-b97d-5a1b21c9c...@openssl.org> on Tue, 25 >>> Sep 2018 13:37:45 +0100, Matt Caswell said:

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message on Tue, 25 Sep 2018 14:15:32 +0100, Matt Caswell said: > On 25/09/18 14:09, Tim Hudson wrote: > > It would also mean our LTS releases are MAJOR.MINOR - as the PATCH is > > the fixes we will apply - so it isn't part of the LTS designation as such. > > e.g. 5.0.x would be the marker -

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message on Tue, 25 Sep 2018 14:11:11 +0100, Matt Caswell said: > > > On 25/09/18 13:54, Richard Levitte wrote: > > In message <896ece72-8923-801e-b97d-5a1b21c9c...@openssl.org> on Tue, 25 > > Sep 2018 13:37:45 +0100, Matt Caswell said: > > > >>> And that is what semantic versioning is

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 13:25, Richard Levitte wrote: > In message on Tue, 25 Sep > 2018 12:22:44 +0100, Matt Caswell said: > >> >> >> On 25/09/18 12:12, Richard Levitte wrote: >>> In message <98774a3e-d127-dcd9-c835-3b359d69b...@openssl.org> on Tue, 25 >>> Sep 2018 11:53:48 +0100, Matt Caswell said:

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 14:09, Tim Hudson wrote: > On Tue, Sep 25, 2018 at 11:02 PM Matt Caswell > wrote: > > You're right on this one. I misread the diff. > > > Not a problem - you are doing the look-at-what-we-did and how it would > be impacted - and that is certainly what

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 13:54, Richard Levitte wrote: > In message <896ece72-8923-801e-b97d-5a1b21c9c...@openssl.org> on Tue, 25 Sep > 2018 13:37:45 +0100, Matt Caswell said: > >>> And that is what semantic versioning is about - it is about the API. >>> So if you add to the API you change either MINOR

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Tim Hudson
On Tue, Sep 25, 2018 at 11:02 PM Matt Caswell wrote: > You're right on this one. I misread the diff. > Not a problem - you are doing the look-at-what-we-did and how it would be impacted - and that is certainly what we should be doing - working through what impact this would have had. Semantic

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 13:56, Tim Hudson wrote: > On Tue, Sep 25, 2018 at 10:37 PM Matt Caswell > wrote: > > - Added some new macros: > https://github.com/openssl/openssl/pull/6037 > > > No we didn't change our public API for this one - we changed *internals*. > The

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Tim Hudson
On Tue, Sep 25, 2018 at 10:37 PM Matt Caswell wrote: > - Added some new macros: > https://github.com/openssl/openssl/pull/6037 No we didn't change our public API for this one - we changed *internals*. The change to include/openssl/crypto.h was entirely changing *comments* to document that the

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message <896ece72-8923-801e-b97d-5a1b21c9c...@openssl.org> on Tue, 25 Sep 2018 13:37:45 +0100, Matt Caswell said: > > And that is what semantic versioning is about - it is about the API. > > So if you add to the API you change either MINOR or MAJOR. > > In your scenario the moment you need

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 13:03, Tim Hudson wrote: > On Tue, Sep 25, 2018 at 9:22 PM Matt Caswell > wrote: > > Lets imagine we release version 5.0.0. We create a branch for it and > declare a support period. Its an LTS release. This is a *stable* > release, so we

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message on Tue, 25 Sep 2018 12:22:44 +0100, Matt Caswell said: > > > On 25/09/18 12:12, Richard Levitte wrote: > > In message <98774a3e-d127-dcd9-c835-3b359d69b...@openssl.org> on Tue, 25 > > Sep 2018 11:53:48 +0100, Matt Caswell said: > > > >> > >> > >> On 25/09/18 11:48, Richard

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Tim Hudson
On Tue, Sep 25, 2018 at 9:22 PM Matt Caswell wrote: > Lets imagine we release version 5.0.0. We create a branch for it and > declare a support period. Its an LTS release. This is a *stable* > release, so we shouldn't de-stabilise it by adding new features. > > Later we do some work on some new

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 12:12, Richard Levitte wrote: > In message <98774a3e-d127-dcd9-c835-3b359d69b...@openssl.org> on Tue, 25 Sep > 2018 11:53:48 +0100, Matt Caswell said: > >> >> >> On 25/09/18 11:48, Richard Levitte wrote: >>> In message on Tue, 25 >>> Sep 2018 11:30:39 +0100, Matt Caswell said:

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message <98774a3e-d127-dcd9-c835-3b359d69b...@openssl.org> on Tue, 25 Sep 2018 11:53:48 +0100, Matt Caswell said: > > > On 25/09/18 11:48, Richard Levitte wrote: > > In message on Tue, 25 > > Sep 2018 11:30:39 +0100, Matt Caswell said: > > > >> > >> > >> On 25/09/18 11:13, Tim Hudson

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 11:48, Richard Levitte wrote: > In message on Tue, 25 Sep > 2018 11:30:39 +0100, Matt Caswell said: > >> >> >> On 25/09/18 11:13, Tim Hudson wrote: >>> On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell >> > wrote: >>> >>> On 25/09/18 10:58, Tim Hudson

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message on Tue, 25 Sep 2018 11:30:39 +0100, Matt Caswell said: > > > On 25/09/18 11:13, Tim Hudson wrote: > > On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell > > wrote: > > > > On 25/09/18 10:58, Tim Hudson wrote: > > > On Tue, Sep 25, 2018 at 7:23 PM

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 11:13, Tim Hudson wrote: > On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell > wrote: > > On 25/09/18 10:58, Tim Hudson wrote: > > On Tue, Sep 25, 2018 at 7:23 PM Richard Levitte > mailto:levi...@openssl.org> > >

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Tim Hudson
On Tue, Sep 25, 2018 at 8:07 PM Matt Caswell wrote: > On 25/09/18 10:58, Tim Hudson wrote: > > On Tue, Sep 25, 2018 at 7:23 PM Richard Levitte > > wrote: > > > > So what you suggest (and what I'm leaning toward) means that we will > > change our habits. > > >

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Matt Caswell
On 25/09/18 10:58, Tim Hudson wrote: > On Tue, Sep 25, 2018 at 7:23 PM Richard Levitte > wrote: > > So what you suggest (and what I'm leaning toward) means that we will > change our habits. > > > Adoption of semantic versioning will indeed require us to

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Tim Hudson
On Tue, Sep 25, 2018 at 7:23 PM Richard Levitte wrote: > So what you suggest (and what I'm leaning toward) means that we will > change our habits. > Adoption of semantic versioning will indeed require us to change our habits in a number of areas - that is the point of having a single clear

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message on Tue, 25 Sep 2018 18:39:43 +1000, Tim Hudson said: > A fairly common approach that is used is that you can only remove something > that has been > marked for deprecation at a MAJOR release version boundary. > > That is entirely independent of the semantic versioning view of

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Tim Hudson
A fairly common approach that is used is that you can only remove something that has been marked for deprecation at a MAJOR release version boundary. That is entirely independent of the semantic versioning view of things - which also happens to say the same thing (that adding a deprecation

Re: [openssl-project] Release strategy updates & other policies

2018-09-25 Thread Richard Levitte
In message <20180924.13.2155153469056385673.levi...@openssl.org> on Mon, 24 Sep 2018 10:00:03 +0200 (CEST), Richard Levitte said: > In message <79590c7b-98a4-4816-9eea-52f21b5e23e1@default> on Sun, 23 Sep 2018 > 20:37:46 -0700 (PDT), Paul Dale said: > ... > > Some thoughts about this: >

Re: [openssl-project] Release strategy updates & other policies

2018-09-24 Thread Richard Levitte
In message <79590c7b-98a4-4816-9eea-52f21b5e23e1@default> on Sun, 23 Sep 2018 20:37:46 -0700 (PDT), Paul Dale said: > While reading through the lively versioning discussions, it appears > that there are some fundamentals that seem to lack surrounding > policies and guidance. True, we do need

Re: [openssl-project] Release strategy updates & other policies

2018-09-23 Thread Paul Dale
yption Phone +61 7 3031 7217 Oracle Australia -Original Message- From: Matt Caswell [mailto:m...@openssl.org] Sent: Friday, 21 September 2018 11:19 PM To: openssl-project@openssl.org Subject: [openssl-project] Release strategy updates I am very concerned about stability of

[openssl-project] Release strategy updates

2018-09-21 Thread Matt Caswell
I am very concerned about stability of our API moving forwards. There are various discussions about changing the version number to 1.2.0 (or possibly 2.0.0) - which according to our versioning scheme would allow breaking changes. Whilst this is true I think we need to be very wary about "opening