Release Testing Help wanted
You’ve been reporting bugs via Github and the Forums. Our team has been busy collaborating with community members to get fixes prepared. We need your help to test the release alongside our QA cohort and team.
Key Dates:
Code Freeze: 10th April 2014
Testing: 14th to 20th April 2014
Community Co-testing Day: 16th April 2014
Fixes: 21st April 2014
Crowdmap Classic Upgrade: 22nd April 2014
Crowdmap Classic Tests & Overview: 23rd April 2014
2.7.3 Release: 23rd April 2014
Community Test Day
Testing is more fun when we do it together. The Ushahidi team will be online to co-test. Join Us.
Date: Wednesday, April 16, 2014 / Thursday, April 17, 2014
Times: Wednesday, April 16, 09:00 EAT to Thursday, April 17, 2014 12:00 pm EAT
Your Local Time: http://bit.ly/1ij228f to http://bit.ly/1t1nV0u
To join this virtual online event, login to skype or irc. See Contact Us for details to find how how to connect. Introduce yourself. See the main bug tracking spreadsheet(below) or tagged github items (below). Add your items. Ask questions
How to help
If you are a server ninja, you can download the release candidate and test away. We also have a test server with you can simply login and be a pirate tester. Reminder: Crowdmap Classic uses the same software code base as Ushahidi platform, so testing.ushahidi.com will be almost like testing on Crowdmap Classic.
Reporting a Bug
We are asking all bugs to be flagged on the spreadsheet. Report a bug guidelines
Here are some top level items:
General Fixes
- Category import on CSV import:
- Broken video embeds in reports when viewed over HTTPS:
- Install errors: 1321 and 1337
- Dual alert sign-up: 1316 and 1339
- Links back to reports – smssync: SMSSync #140 and Ushahidi #1334
- Parent category list in edit report new category
- Timeline upgrade
Thanks in advance to all those who reported these bugs, helped fix and test them.