GTD Tracks blog: Upgrade Issues

Upgrade Issues

Ryan — Fri, 28 Jul 2006 16:08:00 -0400

If you’re seeing wierd XML files coming at you after this latest upgrade, you’re going to need to logout and log back in as some URLs have changed underneath you.

This issue has made me realize that I need to be stricter in when I roll out new features. The Tracks codebase just moves so quickly I get a little too excited.

I think I’m going to start limiting myself to one upgrade per week – maybe on Sunday nights so unexpected things like this don’t happen and tarnish the user experience. I’ll also publish a post here letting you know what’s coming down the pipe.

My apologies!

"Upgrade Issues" by Jim Van Fleet

Sun, 30 Jul 2006 09:02:20 -0400

This also applies if you’re just getting yourself set up for the first time. Use the handy logout link on this page!

"Upgrade Issues" by Ryan Daigle

Sat, 29 Jul 2006 09:54:56 -0400

I agree Luke. Right now I’m running through a set of manual functionaly, deployment and data integrity checks, but an automated plan is definitely in the works.

"Upgrade Issues" by Luke Melia

Fri, 28 Jul 2006 17:19:48 -0400

Ryan, remember that there’s no particular quality guarantee with Tracks trunk. We obviously endeavor to commit clean working code, but I’ve got no one reviewing before I commit, no pair programmer for the most part, no discipline with regard to test-first (I hope to improve on this!), and to boot I do most of my work late at night when I’m tired.

All of this to say that if you’re going to charge money for hosting and you plan to deploy tracks trunk, you should probably create a formal test plan that you run through to ensure that you’ve got a stable build. Your customers will thank you, and I’ll thank you for the patches and bug reports!