[tsc-devel] Backward compatibility and 2.x / 3.x series
Quintus |
Wed, 11 Feb 2015 23:02:29 UTC
Hi everyone,
I have noticed we have some problem with regard to our backward
compatibility conception. Last evidence was in ticket #354[1].
We are in the beta phase of 2.0.0 already and I don’t want to throw it
all around and introduce major code changes now while we are bugfixing
mainly (and replacing Marioesk music). The 2.0.0 release is basically
the completion of the SMC series, and for our first release I think it
is important to allow users of the old SMC game to easily “upgrade”. Old
SMC is, as far as I can tell, still pretty commonly used so I think it’s
better if we take those people with us without having them to guide
through some level format conversion tool for now.
I don’t think the 2.x series will last long anyway. Our tracker is full
of feature requests[2], some of which require breaking existing code,
and we still have too much legacy code in the codebase as too just
shifting it around with us. After the 2.0.0 release, I imagine we’re
going to implement features for 2.1.0 quickly, and simultaneously start
a 3.0.0 development branch in which we implement the
backward-compatibility breaks. Under this conception we probably only
have some few releases in the 2.x series.
We will also probably suffer from a credibility damage if we stopped
beta and went back into development again. Who has ever seen such a
thing?
Valete,
Quintus
(whose email signature is becoming far too long)
[1]: https://github.com/Secretchronicles/TSC/issues/354
[2]: https://github.com/Secretchronicles/TSC/labels/Feature
--
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