On the back of feedback in the last post’s comments it was clear GTDInbox wasn’t working well for everyone, so I’ve updated GTDInbox to smooth over a few more sharp edges. Thanks for your patience with this!

To re-iterate the earlier disclaimer; I think that until the latest round of major updates are complete (in GTDInbox – although the same is true of Gmail!), we may continue to have less than 100% stability. I’ll post an update on where we’re at with 2.1 later in the week (but it’s progressing well).

To upgrade to 2.0.11.5, just go to http://www.gtdinbox.com/ and click the green button.

GTDInbox 2.1 testers, I hope you still have your emails with the details on how to download it. Just go to the new website and grab 2.1a5 (again, the green button).

2.1a4 (for donators) and 2.0.11.4 are now ready. They’ve been extensively patched to work with the latest Gmail change (see the previous blog post); and also had a few other rough edges ironed out – for one, I hope the people who have suffered labelling issues will now have an easier life!

To re-iterate an earlier disclaimer; I think that until the latest round of major updates are complete (in GTDInbox – although the same is true of Gmail!), we may continue to have less than 100% stability. I’ll post an update on where we’re at with 2.1 later in the week (but it’s progressing well).

To upgrade to 2.0.11.4, just go to http://www.gtdinbox.com/ and click the green button.

GTDInbox 2.1 testers, I hope you still have your emails with the details on how to download it. Just go to the new website and grab 2.1a4 (again, the green button).

The most recent fail is a beauty – absolutely nothing I can tell has visibly changed, but they’ve changed 95% of all interface-code behind the scenes. As you can no doubt imagine I was chuckling heartily at this news this morning

I was hoping to have it all fixed up before it affected everyone; but it’s a rather hefty job (pretty much every single part of GTDInbox has been hit).

Hopefully I’ll have it running by tomorrow morning (GMT).

It appears there were  a few – much less noticeable – aftershocks to last week’s Gmail update, and GTDInbox was left in a weakened state! I’ve polished it up again, and the downloads are now available.

It’s a little bit of bad timing, because every time I have to patch the current version of GTDInbox, time is taken away from building the major updates (which frustratingly, wouldn’t be so thrown by Gmail’s recent changes – but that’s a frustration I’ll be able to live with once this is all behind us!). Essentially, our resources are a little tight, but we’re cracking on as quickly as we can!

Thanks to everyone who emailed me and commented on the blog about their issues – it helped me get to the bottom of what was going on. As a disclaimer, I think things may continue to be a little shakey for the next few weeks, but I’ll try and get on top of every issue as it appears.

To upgrade to 2.0.11.3, just go to http://www.gtdinbox.com/ and click the green button.

GTDInbox 2.1 testers, I hope you still have your emails with the details on how to download it. Just go to the new website and grab 2.1a2 (again, the green button).

Phew Ok, that was a tough slog – I had to rewrite some key components to account for Gmail’s new UI – but (I hope) we now have a working pair of releases.

The ‘even better’ news is that we’ve learnt plenty about what can go wrong, so as we prepare major updates to 2.1 we are making it more robust against future Gmail changes.

To upgrade to 2.0.11.2, just go to http://www.gtdinbox.com/ and click the green button.

GTDInbox 2.1 testers, I hope you still have your emails with the details on how to download it. Just go to the new website and grab 2.1a2 (again, the green button). If you have donated in the last few days to help us out (and a huge thanks to those who did – it was a great morale booster), you should be getting emails shortly with details on how to access 2.1.

Update (05/2/2009 – 5 mins later)

I wanted to add – a big thanks to everyone who sent supportive emails and posted nice comments on the earlier blog post – the community’s support is, as always, very appreciated.

Just a quick service announcement – only just spotted this, so it’s caught me on the back foot. Will try and get both 2.0.11.1 and 2.1 repaired today.

Update 04/01/2009 – 23:00

It’s taking longer than expected – some fairly deep code changes having to happen. Testing now, so should be ready to release in early Thursday am. Thanks for all the messages of support! (Oh, and plenty being learnt – as we do with every break – about how to handle changes better in the future).