Archive for April, 2008

How to backup your data prior to testing

I think many people are hesitant to jump into testing because everyone knows that the nightly builds are  by definition, unstable, and people already have their channels set up just as they like them.

There are two ways you can preserve and restore your data prior to starting a test run, OPML export, or by copying off your database.

Export Channels OPML

This option is built into miro and can be accomplished as easily as going to the Channels menu and selecting Export Channels (OPML)… . This will create a list of your channels and channel folders that you save off to your system. You can then import the list at any time using the Channels menu and selecting Import Channels (OPML)… .

Using this, will only save off your channel list. If you delete your database, and start over with a clean system, Importing the channels via OPML will not preserve the downloaded, watched or unwatched status of videos in each channel.

Database Backup and Restore

Currently database backup is still a manual process and the location varies with your operating system.

  • Windows XP: C:\\Documents and Settings\(you)\Application Data\Participatory Culture Foundation \Miro\Support\sqlitedb
  • Vista: C:\\Users\(you)\AppData\Roaming\Participatory Culture Foundation\Miro\Support\sqlitedb
  • OS X: /Users/(you)/Library/Application Support/Miro/sqlitedb
  • GTKX11: ~yourhome/.miro/sqlitedb

Just copy your sqlitedb file to a safe location on your system.  If something goes wrong during testing - you can do a fresh install, copy your database back to the original location, restart Miro and be back up and running.

* Note:  If you migrated your movie storage - restoring the old db would cause it to lose track of those items.

I hope these two options make you feel a little more comfortable about diving in to some of the testing builds.  If anyone out there wants to help make the backup / restore process a little less manual - reply to this post.

Global Happy Hour

Leading up to the 1.2.3 release, I was really happy to see that some new people signed up and helped us with the regression testing.

New testers like jan.s,  fixitguy, fox.box, tbutterfoss and strash joined some of our regular testers like i_therain, sedatg and elmargol to help get this release out.  I also received some emails from a few people who didn’t get a chance this time, but would still like to in the future.

Right now is a really exciting time to be part of the Miro QA team.  As a Webware 100 winner, it is official:  We ARE are one of the coolest apps in town.   If you would like to be part of the Miro QA team you should do these three things:

  1. Go to the QA wiki to browse our to do list.
  2. Sign up for the tester mailing list to stay up to date on our activities.
  3. Join us for a global chat on the Miro chat channel  (or join irc.freenode.org #miro) this Friday at 7:00 PM GMT.  This is 9:00 PM CEST, 8:00 PM BST,  3:00 PM EST, 12:00 PM PST.

I can’t really buy anyone a beer from here, but you can BYO.  I’d love to meet you, answer any questions you might have and share ideas about how we can continue to improve Miro QA.

testing, testing 123

I’d like to believe that we did the update releases for 1.2 just so that we could say that a few times… but we didn’t.

As I explained in an email to the mailing list, we really need to get more people involved in the testing so that we get more systems variation.

So I am hoping that some up you can help out by picking up the rc build, for your respective os and run the Quicktest for 1.2.3 rc0.

If you have time to help - drop a line here, send me an email jed [at] pculture [dot] org, or just find me on the irc (irc.freenode.org #miro).