, Leif Hedstrom wrote:
> From: Leif Hedstrom
> Subject: [RESULT][VOTE] Release Apache Traffic Server v3.0.0
> To: dev@trafficserver.apache.org
> Cc: "'us...@trafficserver.apache.org'" ,
> "Sally Khudairi"
> Date: Monday, June 13, 2011, 6:00
Original Message
Subject: [ANNOUNCE] The Apache Software Foundation Announces Apache
Traffic Server v3.0.0
Date: Tue, 14 Jun 2011 08:10:35 -0700 (PDT)
From: Sally Khudairi
Reply-To: s...@apache.org
To: annou...@apache.org
[this announcement available
On 06/09/2011 03:50 PM, Leif Hedstrom wrote:
Hi all,
I've prepared a package for a v3.0.0 release. Please take a look at
the artifacts, check the STATUS/README/CHANGES files, and do builds
and tests. After finishing your examination of the release candidate,
please cast your ±/0 vot
+1
On Thu, Jun 9, 2011 at 5:50 PM, Leif Hedstrom wrote:
> Hi all,
>
> I've prepared a package for a v3.0.0 release. Please take a look at the
> artifacts, check the STATUS/README/CHANGES files, and do builds and tests.
> After finishing your examination of the release candida
+1
On Sun, Jun 12, 2011 at 8:06 PM, Leif Hedstrom wrote:
> On 06/09/2011 03:50 PM, Leif Hedstrom wrote:
>
>> Hi all,
>>
>> I've prepared a package for a v3.0.0 release. Please take a look at the
>> artifacts, check the STATUS/README/CHANGES files, and do b
On 06/09/2011 03:50 PM, Leif Hedstrom wrote:
Hi all,
I've prepared a package for a v3.0.0 release. Please take a look at
the artifacts, check the STATUS/README/CHANGES files, and do builds
and tests. After finishing your examination of the release candidate,
please cast your ±/0 vot
+1
Built on solaris 10 (64-bit), regression tests passed.
On Thu, Jun 9, 2011 at 5:50 PM, Leif Hedstrom wrote:
> Hi all,
>
> I've prepared a package for a v3.0.0 release. Please take a look at the
> artifacts, check the STATUS/README/CHANGES files, and do builds and tests.
On 06/09/2011 03:50 PM, Leif Hedstrom wrote:
Hi all,
I've prepared a package for a v3.0.0 release. Please take a look at
the artifacts, check the STATUS/README/CHANGES files, and do builds
and tests. After finishing your examination of the release candidate,
please cast your ±/0 vot
- Original Message -
> Hi all,
>
> I've prepared a package for a v3.0.0 release. Please take a look at
> the
> artifacts, check the STATUS/README/CHANGES files, and do builds and
> tests. After finishing your examination of the release candidate,
> please
>
an is that we'll make an official v3.0.0
announcement with the ASF press organization on 6/14.
Well, here is the list of changes since 2.1.9:
*) [TS-827] TSMimeHdrFieldValueStringInsert() can use freed memory to
edit headers. Author: William Bardwell.
*) [TS-825] negative cach
Hi all,
I've prepared a package for a v3.0.0 release. Please take a look at the
artifacts, check the STATUS/README/CHANGES files, and do builds and
tests. After finishing your examination of the release candidate, please
cast your ±/0 votes, I will call the vote on 6/13/2011. The src tar
Hi all,
this is a "last call", does anyone have any concerns with the following
release schedule for v3.0.0:
Thursday 6/9: We prep the 3.0.0 release candidate, and make it available.
Monday 6/13: In the evening, assuming the vote passes, we push to dist.
Tuesday 6/14: Sally Khudar
> So please, if v2.1 really is (almost) as stable as v2.0 -- get a new
> stable release out ASAP, so that we can start seriously considering
> it.
I dare claim 2.1.9 is without a doubt much more stable than the 2.0
release. The reason we call it -unstable is that the *API* has not
been stabilise
gt; ~1-2 weeks. I know we have unresolved issues, but I'd like to get the
> input here from our users and devs. A few items to discsuss on
>
>
> 1. Is the 3.0.x branch good enough for a first v3.0.0 release?
> 2. If not, should we make another v2.1.10 release first?
> 3. P
iscsuss on
1. Is the 3.0.x branch good enough for a first v3.0.0 release?
2. If not, should we make another v2.1.10 release first?
3. People with unresolved bugs, would you be ok with a v3.0.0 release
now, and hopefully a v3.0.1 release 4-6 weeks after that (assuming we
can gather details on any press
I've been lurking since ATS was announced, and am still waiting for a
proper stable release. I work for an ISP, and would like to use ATS
for various proxies and caches, but can't run an "unstable" release
and I can't set up a new platform without IPv6 support. Therefore
we're still rolling out s
Hi all,
I'd like to start a discussion on the viability of a 3.0.0 release in
~1-2 weeks. I know we have unresolved issues, but I'd like to get the
input here from our users and devs. A few items to discsuss on
1. Is the 3.0.x branch good enough for a first v3.0.0 release?
2. If n
17 matches
Mail list logo
