Re: Release 2.12 - 3.0
--000e0cd48f9cc0dbc604af9e1dcc
Content-Type: text/plain; charset=ISO-8859-1
This is where I saw "I TOLD you so!" and quietly stare at everyone with a
smug look, cause I had proposed yearly release cycles just last month.
Please don't smack me for it.
Seriously, though:
If we continue to test master relentlessly - which several people are
already doing - we should be able to identify any problems from the new code
relatively quickly.
I had already put together "release candidate" versions of 2.12, since
almost all bugs tied to 2.12 were cleared. In fact, I already have a
complete pkgsrc-2011Q3 package build for i386/x86_64 done on 2.11, which
will work for 2.12 or master.
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.
On Tue, Oct 18, 2011 at 5:22 PM, Samuel J. Greear <sjg@evilcode.net> wrote:
> If we are voting, I like E. But Justin is the release engineer this
> cycle and I think he should decide. That said, I am sure he values all
> of this input.
>
> Sam
>
--000e0cd48f9cc0dbc604af9e1dcc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
This is where I saw "I TOLD you so!" and quietly stare at everyon=
e with a smug look, cause I had proposed yearly release cycles just last mo=
nth.=A0 Please don't smack me for it.<br><br>Seriously, though:<br><br>
If we continue to test master relentlessly - which several people are alrea=
dy doing - we should be able to identify any problems from the new code rel=
atively quickly.<br><br>I had already put together "release candidate&=
quot; versions of 2.12, since almost all bugs tied to 2.12 were cleared.=A0=
In fact, I already have a complete pkgsrc-2011Q3 package build for i386/x8=
6_64 done on 2.11, which will work for 2.12 or master.=A0 <br>
<br>Having a nifty new software version with potential bugs is not unique t=
o our software project.=A0 Let's do what other projects do: say "H=
ere's the new version.=A0 It's in beta.=A0 It has a lot of new feat=
ures, but may have new bugs.=A0 Please test".=A0 That way we're no=
t releasing with a known nasty bug, but we're not shutting off access t=
o an already wildly improved next release.<br>
<br><div class=3D"gmail_quote">On Tue, Oct 18, 2011 at 5:22 PM, Samuel J. G=
reear <span dir=3D"ltr"><<a href=3D"mailto:sjg@evilcode.net">sjg@evilcod=
e.net</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If we are voting, I like E. But Justin is the release engineer this<br>
cycle and I think he should decide. That said, I am sure he values all<br>
of this input.<br>
<br>
Sam<br>
</blockquote></div><br>
--000e0cd48f9cc0dbc604af9e1dcc--
討論串 (同標題文章)
完整討論串 (本文為第 15 之 19 篇)：