Re: [tsc-devel] [ANN] TSC 2.0.0 RC1 released

Chris Jacobsen | Wed, 29 Jul 2015 05:57:01 UTC

> Yes, that’s how it was planned. Because if no issues are found, why
issue another release candidate with the exact same code? However,

> if it appears indeed difficult to reach mrvertigo, we can still decide
to prolong the RC1 phase by two weeks or so. I’d rather not do this,
though.

I've emailed Mr. Vertigo and created a forum post that @'s people who might be able to
help us with testing.  Let's wait some days and see who responds.  We can
then make a collective decision as to how to proceed with the release date.

I understand why everyone is eager to be done with release 2.0.  However, I do think we
need to at least verify some people have been able to test the release candidate before 
releasing it.  Otherwise there is a higher chance of an unstable release.  This would go
against a lot of work we've put into the release up to this point.


> Well, “beta” phase is over now. There was plenty of time to do beta
testing — and there was, just see how many issues we fixed — and the
code now is in a fairly releasable state, with only minor issues left
that will go into the next release. So unless a real big problem occurs,
the code we have now is the code for the final 2.0.0 release.

Yes, I used the wrong term.  It is "release candidate testing".  If we are able to use this executable
for the release that is great.  We just need to be sure it's stable.

-datahead





On Tuesday, July 28, 2015 4:52 AM, Quintus <…s@q…> wrote:



Chris Jacobsen <…9@y…> writes:

> If I understand correctly, if no issues are found in this release
> candidate, we will skip release candidate 2 and publish the release to
> all distribution channels, correct?In that case, the potential final
> release date is two weeks from 07-27-2015, correct?

Yes, that’s how it was planned. Because if no issues are found, why
issue another release candidate with the exact same code? However,

> I just want to make sure I communicate all of this to Mr. Vertigo
> correctly when I try to email him. However, if it is likely we may be
> done in two weeks, we aren't going to have any time for him to
> respond, since we need to allow 1-2 weeks to try and get a hold of
> him. We might have to consider allowing more testing time if we want
> YouTubers to test (though we should first see if we reach him).

if it appears indeed difficult to reach mrvertigo, we can still decide
to prolong the RC1 phase by two weeks or so. I’d rather not do this,
though.

> I can also try to contact others such as DevEd about beta testing.

Well, “beta” phase is over now. There was plenty of time to do beta
testing — and there was, just see how many issues we fixed — and the
code now is in a fairly releasable state, with only minor issues left
that will go into the next release. So unless a real big problem occurs,
the code we have now is the code for the final 2.0.0 release.

> -datahead

Vale,

Quintus

-- 
#!/sbin/quintus
Blog: http://www.guelkerdev.de

GnuPG key: F1D8799FBCC8BC4F