On 4/30/13 6:13 PM, Leif Hedstrom wrote:
ing what the users of ATS have to say about this.
Indeed. Debian (and its users) for example will get ATS 3.0 when the new
stable version will be released presumably this week with its own 3 year
cycle to start right then.
All excellent points.
Ok, so
On 4/30/13 5:09 AM, Arno Töll wrote:
Hi,
On 30.04.2013 12:33, Daniel Gruno wrote:
This
would however mean that we have a two year support frame for released
products, which may or may not be enough for some people, so I'd be
interested in hearing what the users of ATS have to say about this.
I
On Apr 29, 2013, at 11:22 PM, Igor Galić wrote:
>
>
> - Original Message -
>> Updated Branches:
>> refs/heads/master 54b532b64 -> d8c526233
>>
>>
>> TS-1864 Rearrange some of the autoconf code, order matters
>>
> [snip]
>> Branch: refs/heads/master
>> Commit: d8c5262331e065409764098
Hi,
On 30.04.2013 12:33, Daniel Gruno wrote:
> This
> would however mean that we have a two year support frame for released
> products, which may or may not be enough for some people, so I'd be
> interested in hearing what the users of ATS have to say about this.
Indeed. Debian (and its users) fo
On 04/30/2013 04:47 AM, Leif Hedstrom wrote:
> Hi all,
>
> I'd like to propose that we EOL support for ATS v3.0 soon after we
> release v3.4.0. That would be around the June / July time frame. This
> leaves us with officially support two major releases simultaneously at
> any give time, plus the
On 30 Apr 2013, at 01:44, Brian Geffon wrote:
> Hello All,
> I think we have a major flaw in first_write_block() in MIOBuffer, the
> comment and code are the following:
Ref: thread on this list about a week ago,
"TS API won't return header data of > 4K".
Your patch looks right, but then so did
