Re: Release 2.12 - 3.0
--000e0cd3b4a8dc4c0604afb09797
Content-Type: text/plain; charset=ISO-8859-1
Lemme clarify. We don't release until we know it's stable, but we make sure
there's images available of DragonFly with the new code to point people at
when they say "I want to test" or "hey I can't get 2.10 working on this
hardware". That seems to be what people are mostly working towards anyway.
On Wed, Oct 19, 2011 at 1:42 AM, <elekktretterr@exemail.com.au> wrote:
> > Having a nifty new software version with potential bugs is not unique to
> > our
> > software project. Let's do what other projects do: say "Here's the new
> > version. It's in beta. It has a lot of new features, but may have new
> > bugs. Please test". That way we're not releasing with a known nasty
> bug,
> > but we're not shutting off access to an already wildly improved next
> > release.
>
> What would be point of that? Do we absolutely have to do a release? Just
> wait a month to test Matt's new code and release it then. It's either a
> RELEASE or it's BETA. It's not the worst thing to happen to a project to
> have to delay a release because of a known bug.
>
>
--000e0cd3b4a8dc4c0604afb09797
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Lemme clarify.=A0 We don't release until we know it's stable, but w=
e make sure there's images available of DragonFly with the new code to =
point people at when they say "I want to test" or "hey I can=
't get 2.10 working on this hardware".=A0 That seems to be what pe=
ople are mostly working towards anyway.<br>
<br><div class=3D"gmail_quote">On Wed, Oct 19, 2011 at 1:42 AM, <span dir=
=3D"ltr"><<a href=3D"mailto:elekktretterr@exemail.com.au">elekktretterr@=
exemail.com.au</a>></span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">> Having a nifty new software version with potential b=
ugs is not unique to<br>
> our<br>
> software project. =A0Let's do what other projects do: say "He=
re's the new<br>
> version. =A0It's in beta. =A0It has a lot of new features, but may=
have new<br>
> bugs. =A0Please test". =A0That way we're not releasing with a=
known nasty bug,<br>
> but we're not shutting off access to an already wildly improved ne=
xt<br>
> release.<br>
<br>
</div>What would be point of that? Do we absolutely have to do a release? J=
ust<br>
wait a month to test Matt's new code and release it then. It's eith=
er a<br>
RELEASE or it's BETA. It's not the worst thing to happen to a proje=
ct to<br>
have to delay a release because of a known bug.<br>
<br>
</blockquote></div><br>
--000e0cd3b4a8dc4c0604afb09797--
討論串 (同標題文章)
完整討論串 (本文為第 18 之 19 篇)：