Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lethosor]

The Big Wait is going to be a bit of a challenge interest wise. I would advice Toady to keep a copy of the last release before the Big Wait on a USB or similar (e.g. an extra one in addition to the current backup system) so that crash bugs can be fixed in the "old" version (if that had been done, the weapon trap/missile break crash bug could [and should] have been fixed with an emergency release after the 0.43.X arc).

From what I understand, he does make copies of every release. I don't know exactly where I heard that - could have been some interview, or FotF. But without version control, making "small" hotfixes to older releases while working on newer features can quickly turn into larger messes. For trivial changes, it seems like something he should be able to handle, but not all simple issues have trivial fixes, and I don't know exactly what his thoughts are on the matter.

[DG]

You can still download versions as far back as Aug 8 2006 here http://bay12games.com/dwarves/older_versions.html

[lethosor]

You can still download versions as far back as Aug 8 2006 here http://bay12games.com/dwarves/older_versions.html

Right, but those are binaries. PatrikLundell and I are talking about source code.

[Toady One]

The Big Wait is going to be a bit of a challenge interest wise. I would advice Toady to keep a copy of the last release before the Big Wait on a USB or similar (e.g. an extra one in addition to the current backup system) so that crash bugs can be fixed in the "old" version (if that had been done, the weapon trap/missile break crash bug could [and should] have been fixed with an emergency release after the 0.43.X arc).

From what I understand, he does make copies of every release. I don't know exactly where I heard that - could have been some interview, or FotF. But without version control, making "small" hotfixes to older releases while working on newer features can quickly turn into larger messes. For trivial changes, it seems like something he should be able to handle, but not all simple issues have trivial fixes, and I don't know exactly what his thoughts are on the matter.

Yeah, I have all the versions.  Generally, I don't like the idea of maintaining two branches, as it can be an ongoing distraction and momentum killer, but I agree on the weapon trap.  That was too much.  I'll be thinking about it as we approach the transition.

[vanatteveldt]

I'm sure I won't be the first or the last to say this, but version control systems, especially git (with or without github) have come a long way. It's not just useful for co-ordinating bigger teams, but also really useful if you're making something by yourself. Cherry-picking an emergency patch from an old branch to the master is trivial, and you can easily view older versions, revert changes, etc.

(of course, it won't actually solve issues like having to test and build the emergency patch and it also won't help you if the underying code or logic is not the same between branches ... but it will solve all the admin / bookkeeping hassle.)