Ryan Petrello writes:
> Sorry for the late reply to this thread - I was having email access fits for
> most of the summit this past week. I also intend to look at the gate
> failures for py33 and pypy for Noorul's patch. I need to dig a bit and
> figure out what's *actually* going on there,
Sorry for the late reply to this thread - I was having email access fits for
most of the summit this past week. I also intend to look at the gate failures
for py33 and pypy for Noorul's patch. I need to dig a bit and figure out
what's *actually* going on there, as pecan should work just fine f
On Fri, Nov 8, 2013 at 8:02 AM, Jay Pipes wrote:
> On 11/07/2013 06:41 PM, Adrian Otto wrote:
>
>> Solum Team,
>>
>> First of all I wanted to say that I have been thinking a lot about this
>> thread, and have been seeking input from a number of you who attended the
>> Summit this week. I do *not*
On 11/07/2013 06:41 PM, Adrian Otto wrote:
Solum Team,
First of all I wanted to say that I have been thinking a lot about this thread,
and have been seeking input from a number of you who attended the Summit this
week. I do *not* see this decision as a critical one, because if something
reall
Solum Team,
First of all I wanted to say that I have been thinking a lot about this thread,
and have been seeking input from a number of you who attended the Summit this
week. I do *not* see this decision as a critical one, because if something
really mattered a ton we could rip our one framewo
On 11/07/2013 07:28 AM, Jay Pipes wrote:
Hey Doug, following up, but realize you are likely very busy at the
summit :)
On 11/04/2013 10:20 PM, Doug Hellmann wrote:
On Tue, Nov 5, 2013 at 10:37 AM, Jay Pipes declaring the models for the consumer of the API, rather than
the
imp
Hey Doug, following up, but realize you are likely very busy at the
summit :)
On 11/04/2013 10:20 PM, Doug Hellmann wrote:
On Tue, Nov 5, 2013 at 10:37 AM, Jay Pipes
I wasn't referring to the database representation, actually. I was
referring to the data model, which is different in that it
> On Nov 5, 2013, at 11:26 AM, Doug Hellmann
> wrote:
>
>
>
>
>> On Tue, Nov 5, 2013 at 10:37 AM, Jay Pipes wrote:
>> Doug, I respect you very much as an engineer and as a community member, so I
>> want to preface this with a very important dislaimer: don't take these
>> opinions as anyt
On Tue, Nov 5, 2013 at 10:37 AM, Jay Pipes wrote:
> Doug, I respect you very much as an engineer and as a community member, so
> I want to preface this with a very important dislaimer: don't take these
> opinions as anything more than what they are...a discussion of differing
> viewpoints.
>
Dit
On Tue, Nov 5, 2013 at 8:11 AM, Noorul Islam K M wrote:
> Doug Hellmann writes:
>
> > On Sun, Nov 3, 2013 at 10:54 PM, Jay Pipes wrote:
> >
> >> On 11/02/2013 11:26 PM, Russell Bryant wrote:
> >>
> >>> On 11/02/2013 11:54 AM, Adrian Otto wrote:
> >>>
> Noorul,
>
> I agree that ke
Doug, I respect you very much as an engineer and as a community member,
so I want to preface this with a very important dislaimer: don't take
these opinions as anything more than what they are...a discussion of
differing viewpoints.
Comments inline.
On 11/04/2013 06:58 PM, Doug Hellmann wrote
Doug Hellmann writes:
> On Sun, Nov 3, 2013 at 10:54 PM, Jay Pipes wrote:
>
>> On 11/02/2013 11:26 PM, Russell Bryant wrote:
>>
>>> On 11/02/2013 11:54 AM, Adrian Otto wrote:
>>>
Noorul,
I agree that key decisions should be tracked in blueprints. This is the
one for this deci
On Sun, Nov 3, 2013 at 10:54 PM, Jay Pipes wrote:
> On 11/02/2013 11:26 PM, Russell Bryant wrote:
>
>> On 11/02/2013 11:54 AM, Adrian Otto wrote:
>>
>>> Noorul,
>>>
>>> I agree that key decisions should be tracked in blueprints. This is the
>>> one for this decision which was made in our 2013-10-
> On Nov 3, 2013, at 9:02 AM, Jay Pipes wrote:
>
>> On 11/02/2013 11:26 PM, Russell Bryant wrote:
>>> On 11/02/2013 11:54 AM, Adrian Otto wrote:
>>> Noorul,
>>>
>>> I agree that key decisions should be tracked in blueprints. This is the
>>> one for this decision which was made in our 2013-10-1
On Nov 3, 2013, at 6:54 AM, Jay Pipes wrote:
> On 11/02/2013 11:26 PM, Russell Bryant wrote:
>> On 11/02/2013 11:54 AM, Adrian Otto wrote:
>>> Noorul,
>>>
>>> I agree that key decisions should be tracked in blueprints. This is the
>>> one for this decision which was made in our 2013-10-18 publi
On 11/02/2013 11:26 PM, Russell Bryant wrote:
On 11/02/2013 11:54 AM, Adrian Otto wrote:
Noorul,
I agree that key decisions should be tracked in blueprints. This is the
one for this decision which was made in our 2013-10-18 public meeting.
Jay's submission is consistent with the direction indic
On 03/11/13 11:26 +0800, Russell Bryant wrote:
On 11/02/2013 11:54 AM, Adrian Otto wrote:
Noorul,
I agree that key decisions should be tracked in blueprints. This is the
one for this decision which was made in our 2013-10-18 public meeting.
Jay's submission is consistent with the direction indi
Russell Bryant writes:
> On 11/02/2013 11:54 AM, Adrian Otto wrote:
>
>> Noorul,
>>
>> I agree that key decisions should be tracked in blueprints. This is the
>> one for this decision which was made in our 2013-10-18 public meeting.
>> Jay's submission is consistent with the direction indicated
On 11/02/2013 11:54 AM, Adrian Otto wrote:
> Noorul,
>
> I agree that key decisions should be tracked in blueprints. This is the
> one for this decision which was made in our 2013-10-18 public meeting.
> Jay's submission is consistent with the direction indicated by the team.
>
> https://blueprin
19 matches
Mail list logo
