[tsc-devel] Releasing 2.0.0
Quintus |
Sun, 31 May 2015 21:16:05 UTC
Hi everyone,
as you might have noticed, the issue list for the 2.0.0 milestone on the
tracker[1] is empty. This means that we have resolved all tickets
pending for the 2.0.0 release and we can now continue with the 2.0.0
releasing procedure. Have a look at the release plan[2] again if you
are unsure, a short summary follows.
We will now enter the Release Candidate phase. For each release
candidate issued, we wait two weeks if any serious tickets are
opened. If so, the issue must be fixed as soon as possible and a new RC
immediately issued. Then the two-week phase starts again. If the two
weeks pass without serious reports, the final release is made.
That is, we should now find a date to issue the first release candidate
(2.0.0-RC1). This should be some time where at least some of us have
opportunity to monitor the tracker more closely. As for me, I’m pretty
much available during the next weeks, so I will be fine with any
suggestions you make.
For good measure, I will package a last beta version tomorrow containing
all of the recent changes, so that the RC series can start from a clean
slate.
As datahead has suggested, it might be time to call out for mrvertigo
and his YouTube channel after we released the RC1. I’d suggest to wait
until the RC2 or the final release (whatever comes first) though, just
to be sure he’s not going to run into some obvious bug that will give us
bad reputation.
Valete,
Quintus
[1]: https://github.com/Secretchronicles/TSC/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Version+2.0.0%22
[2]: http://www.secretmaryo.org/phpBB3/viewtopic.php?f=1&t=9948
--
Blog: http://www.quintilianus.eu
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung:
https://www.gnupg.org | https://de.wikipedia.org/wiki/GnuPG
My key fingerprint: | Mein Schlüsselabdruck:
B1FE 958E D5E8 468E AA20 | B1FE 958E D5E8 468E AA20
8F4B F1D8 799F BCC8 BC4F | 8F4B F1D8 799F BCC8 BC4F