The next hugin release is on the sprint toward the finish line. The builds become more solid and stable as days go by and Pablo fixes the bugs. He needs your help! Here is how.
- Make sure you start with the most recent snapshot. The latest downloads for Windows and OSX, as well as the instructions for Linux, are posted here.
- Look at the list of known bugs. Specifically, on the bug tracker, select the group 0.7.0 in the drop down menu and click “browse”.
- Choose one bug from that list. Click on it and read the bug report and comments. Determine if you have all it takes to replicate it. Some bugs are applicable only for specific systems. Others have the necessary image files attached. Use common sense, and in doubt just take up another bug.
- Try to reproduce the bug. Follow the instructions posted on the bug report. It’s usually easy, takes only a few minutes and does no harm to your computer. But for safety, make sure you saved all your other work in progress.
- Report your experience back. If you have a Sourceforge account, you can reply in the bug report thread. Alternatively, just share your findings on the hugin-ptx mailing list.
- Be specific. In your report, specify the exact operating system you’re running hugin on and the version of hugin you have tested. You can see the version in the help -> about menu. For example right now I am running Version 0.7.0.2825, or short SVN2825, on a WinXP SP2 box.
At the time of writing, there are 28 bug reports open in the 0.7.0 group. Some might be already solved in the most recent snapshot, but this need to be confirmed by you. Some might still be applicable, and Pablo needs your feedback to know about it. Many are show stoppers.
If four of you take up one bug per day, in one week they will have been all checked and we’ll know how much work is left until release. Assuming no newer bug are found.
This morning, I went through three of them.
- It has taken me five minutes to verify that bug 1077567 is fixed.
- It has taken me five minutes and a little common sense to determine that bug 1742019 is not a show stopper and move it to 0.7.1 group.
- It has taken me five minutes to verify that bug 1224840 is still applicable to SVN2825 on a WinXP SP2, and it is probably a show stopper for release. It won’t be long until it gets Pablo attention.
Which bug will you take up today?