> 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
+1 for release it.
btw, I am going to put v2.1.9 in production and have spread out that
v3.0 will be release in 2weeks, hopes not make any trouble
:D
在 2011-05-31二的 14:13 -0600，Leif Hedstrom写道：
> Hi all,
>
> I'd like to start a discussion on the viability of a 3.0.0 release in
> ~1-2 weeks. I
Yes, do it.
Sascha
>>> Leif Hedstrom 31.05.2011 22:13 >>>
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
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 not, should
