Bugzilla Update

[mark]

Hi all,

First, I'm sorry for the delay in posting this and, in advance, quite sorry for the problem.

Bugzilla has died. In a rather messy and, unfortunately, irrecoverable way. The long story short is that, for historical reasons, it still ran on my personal server. I had a human-error incident with said server the other night and, alas, it was the kind of incident that ended with me accidentally deleting the server and all of its data.

Further unfortunately, I thought it was actually backed up on EBS (one of Amazon's storage systems). It wasn't. (Or well, more accurately, the root volume was -- so I still have /etc and such. But no actual /var/lib/mysql or /home.) I contacted Amazon to ask for help and they heroically tried, but it was to no avail.

In good news, we actually have substantially all of the data collected across our collected email accounts. We can recover things we want to keep, so very little is actually gone.

What's next? Well, we're going to take this time to take a step back and think about how we do bug/task/feature/etc management and how to fit that into the GitHub Issues system. Since we already use GitHub, there would be some advantages to having a centralized system that fits in with the rest of our workflow. (If you've got experience with GitHub Issues and have some advice, please let us know!)

More details will be coming sometime in the next week or two.

Comments

[denise]

I have a feeling denise would be frustrated by it.

It's like you know me or something ;)

I am willing to give it a try, though!

[alexbayleaf]

Yeah it's definitely worth trying if only to help you realise what you really want/need. We did that for a couple of months with Growstuff before we got frustrated, but it did at least help us figure out where the friction points were, which in turn helped us choose PT.