Excerpts from Hayes, Graham's message of 2016-07-26 18:16:16 +:
> On 26/07/2016 18:47, Doug Hellmann wrote:
> > Excerpts from Hayes, Graham's message of 2016-07-26 13:48:35 +:
> >> On 26/07/2016 14:15, Sean Dague wrote:
> >>> On 07/26/2016 08:51 AM, Doug Hellmann wrote:
> >>>
>
>
On 26/07/2016 18:47, Doug Hellmann wrote:
> Excerpts from Hayes, Graham's message of 2016-07-26 13:48:35 +:
>> On 26/07/2016 14:15, Sean Dague wrote:
>>> On 07/26/2016 08:51 AM, Doug Hellmann wrote:
>>>
Given the amount of in-progress work to address the issue you've
raised, I'm
Excerpts from Hayes, Graham's message of 2016-07-26 13:48:35 +:
> On 26/07/2016 14:15, Sean Dague wrote:
> > On 07/26/2016 08:51 AM, Doug Hellmann wrote:
> >
> >>
> >> Given the amount of in-progress work to address the issue you've
> >> raised, I'm not convinced we need a global rule or polic
On 26/07/2016 14:15, Sean Dague wrote:
> On 07/26/2016 08:51 AM, Doug Hellmann wrote:
>
>>
>> Given the amount of in-progress work to address the issue you've
>> raised, I'm not convinced we need a global rule or policy. All of
>> the teams mentioned are working toward the goal of providing stable
On Tuesday, 26 July 2016 13:23:05 CEST Hayes, Graham wrote:
> On 26/07/2016 14:18, Doug Hellmann wrote:
> >>> And just to satisfy my own curiosity, how does someone looking at the
> >>> internals of tempest know what's on the stable API and what's not
> >>> considered stable? Are the parts of the
On 26/07/2016 14:18, Doug Hellmann wrote:
> Excerpts from Luigi Toscano's message of 2016-07-26 15:02:28 +0200:
>> On Tuesday, 26 July 2016 08:34:27 CEST Doug Hellmann wrote:
>>> Excerpts from Andrea Frittoli's message of 2016-07-26 10:24:07 +:
What still requires work in Tempest is t
Excerpts from Luigi Toscano's message of 2016-07-26 15:02:28 +0200:
> On Tuesday, 26 July 2016 08:34:27 CEST Doug Hellmann wrote:
> > Excerpts from Andrea Frittoli's message of 2016-07-26 10:24:07 +:
> > >
> > > What still requires work in Tempest is the stable interface. Because
> > > plugins
On 07/26/2016 08:51 AM, Doug Hellmann wrote:
>
> Given the amount of in-progress work to address the issue you've
> raised, I'm not convinced we need a global rule or policy. All of
> the teams mentioned are working toward the goal of providing stable
> APIs already, and no one seems to be arguin
On Tuesday, 26 July 2016 08:34:27 CEST Doug Hellmann wrote:
> Excerpts from Andrea Frittoli's message of 2016-07-26 10:24:07 +:
> >
> > What still requires work in Tempest is the stable interface. Because
> > plugins are not in the Tempest tree, the QA team recommend that they use
> > only tem
Excerpts from Hayes, Graham's message of 2016-07-25 21:36:29 +:
> Top posting - this is a recap of what has been said, and some
> clarifications
>
> I realise that I was not very clear at the beginning of this process, so
> here is my effort to clarify things, from the ML thread, and the revie
Excerpts from Andrea Frittoli's message of 2016-07-26 10:24:07 +:
> On Mon, Jul 25, 2016 at 10:36 PM Hayes, Graham wrote:
>
> > Top posting - this is a recap of what has been said, and some
> > clarifications
> >
> > I realise that I was not very clear at the beginning of this process, so
> >
On Mon, Jul 25, 2016 at 10:36 PM Hayes, Graham wrote:
> Top posting - this is a recap of what has been said, and some
> clarifications
>
> I realise that I was not very clear at the beginning of this process, so
> here is my effort to clarify things, from the ML thread, and the review.
>
> > .
Hi,
I am reading through the thread, and it puzzles me that I see a lot of
right words about goals but not enough hints on who is going to implement
that. We all love public and stable interfaces, everyone needs it, and I
don’t think anyone works against that goal.
For one, tempest folks
Top posting - this is a recap of what has been said, and some
clarifications
I realise that I was not very clear at the beginning of this process, so
here is my effort to clarify things, from the ML thread, and the review.
> ... does this also include plugins within projects, like storage
>
14 matches
Mail list logo