On Tue, Jan 29, 2019 at 11:31 AM Kurt Roeckx wrote:
> On Tue, Jan 29, 2019 at 02:07:09PM +, Matt Caswell wrote:
> > So I plan to start the vote soon for merging PR#8096 and backporting it
> to
> > 1.1.1. This is a breaking change as previously discussed.
> >
> > My proposed vote text is as
On Tue, Jan 29, 2019 at 01:27:24PM -0600, David Benjamin wrote:
> I think one clear conclusion from this incident is that this sort of
> low-level API should be avoided, or people will use them in finicky ways
> that break unexpectedly when you change things. Better defer such
> mechanisms to when
On Tue, Jan 29, 2019 at 02:07:09PM +, Matt Caswell wrote:
> So I plan to start the vote soon for merging PR#8096 and backporting it to
> 1.1.1. This is a breaking change as previously discussed.
>
> My proposed vote text is as follows. Please let me know asap of any feedback.
> Otherwise I
On Tue, Jan 29, 2019 at 01:27:24PM -0600, David Benjamin wrote:
> On Tue, Jan 29, 2019 at 11:31 AM Kurt Roeckx wrote:
>
> > On Tue, Jan 29, 2019 at 02:07:09PM +, Matt Caswell wrote:
> > > So I plan to start the vote soon for merging PR#8096 and backporting it
> > to
> > > 1.1.1. This is a
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
So I plan to start the vote soon for merging PR#8096 and backporting it to
1.1.1. This is a breaking change as previously discussed.
My proposed vote text is as follows. Please let me know asap of any feedback.
Otherwise I will start the vote soon.
"master and 1.1.1 will be updated to use
