Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Readme file on download page doesn't seem to make clear which changes go w/ which file versions.
I'd suggest 2 files - one for stable & 1 for unstable releases.
But at minimum, should have specified which new features / bug fixes are for latest unstable version. May be reading it wrong, but now I can't tell which is which.
Or maybe there's a change log - somewhere? Could add a prominent link to that, here on forum.
Unstable versions are experimental and therefore less documented than stable releases or release candidates.
If you're interested in more details, you can always have a look at the commit history here: http://sourceforge.net/p/greenshot/code/commit_browser
If users are going to try / test unstable versions, shouldn't they know what the supposed changes are, to see if the changes / features work as described?
Unstable versions are not release candidates. If we handled every unstable version like a release canidate, there would be far less of them. Plus: we'd have less time to do the actual programming.
Our intention in releasing those is not that everybody tests every change that has been made. There are good chances that stuff is still buggy, so that having few testers is enough at this stage.
Anyone can have a look at the readme file and check out whichever feature they are interested in. People who have reported problems with an unstable version will be informed of any progress in the ticket related to their problem.