1.1 Release Candidate Testing
Posted by Janet
We are ready for Miro 1.1 RC testing to begin. You can run the tests in litmus – I recommend the 1.1 pre-Release testing, test run. Start with the Quicktest then move to the New Feature and Bug Fixes section.
The biggest change for 1.1 relates to torrent downloads. We have switched over to using libtorrent, and have implemented some long asked for options. You can now control both the upload and the download rates or torrents. We also display the total number of seeders and leechers.
Other changes include updates to the navigation buttons on the Guide so that the forward, back and home will work for any additional guides added to Miro. We have also implemented a combined search feature.
You can check out the weekly testing page for a more complete summary of changes.
If anyone wants to help out with the creation of more tests, please let me know. You can reply here.
January 6th, 2008 at 9:31 am
[...] You can find specific details about the testing needed for the upcoming 1.1 release on The Miro Testing Blog! [...]
January 6th, 2008 at 3:11 pm
Testing under linux would be a lot easier if you could provide precompiled builds for the major distributions.
Aren’t there any autobuild services out there?
January 7th, 2008 at 7:21 am
Rich – we do have a good instruction set for building under linux – you can find it here: https://develop.participatoryculture.org/trac/democracy/wiki/GTKX11BuildDocs
I also want to point out that building takes longer now that we are using libtorrent.
January 7th, 2008 at 10:13 pm
I would love to help out, but I’m not completely sure what to do. Should I download the source code in the original post or follow the instructions for getting the source from the link in your last post? If I download the source in the initial post, do I still do “cd tv/platform/gtk-x11
./run.sh” to run it?
I’ve never tested anything before (I know you said that doesn’t matter) and I would just like to know what I’m doing before I try to do it.
January 8th, 2008 at 8:05 am
Hi Tommy –
You should use the source for the release candidate build that is posted on the nightlies page: http://participatoryculture.org/nightlies.
From there you can use ./run.sh as you mentioned above.
There are some test cases that we are hoping people will run on litmus.pculture.org.
Thanks for being involved!
January 9th, 2008 at 9:15 am
[...] ← 1.1 Release Candidate Testing [...]
January 13th, 2008 at 7:43 pm
When I download the source (1.1) under the sticky files section on the nightlies page, it works fine, but when I try to download the source from the build files section below that I just get an empty archive. Should I just be using the one under the stickes section?
January 14th, 2008 at 4:15 am
When doing the release testing – using the sticky section is the best. The nightly builds in the other section should always be regarded as questionable. So always back up your database before testing with them. If you do find a problem – please report it.
We have released 1.1 – so our next focus will be the regular nightly build testing.
January 31st, 2008 at 10:05 pm
Opensuse supplies a build service which works for multiple linux distributions.
Miro/Democracy Player has had quite a set of linux problems in the 1.0 release. You need to improve your release quality here.
Also the Miro forum seems to have no Miro participants on it so that problems highlighted on the forum don’t even seem to enter your release process.
January 31st, 2008 at 10:15 pm
Here is the link to the Suse Build Service, which can build Miro packages for many different Linux Distributions.
http://en.opensuse.org/Build_Service
February 1st, 2008 at 6:59 am
I agree that we can use better coverage testing the various linux platforms.
It would be great if there were more linux volunteers who are willing to build from source and test out the application as we make changes.
A source nightly build is posted along with the windows and os x builds every day.