Bugzilla – Bug 8672
Getting Started Document Review
Last modified: 2009-09-08 09:18:05 UTC
The 7.1 changelog is currently at http://svn.slimdevices.com/repos/slim/7.1/trunk/server/Changelog7.html. In the Getting Started document, the URL points to the old location of http://svn.slimdevices.com/repos/slim/7.1/tags/7.1/server/Changelog7.html
As 7.1 gets closer to release, I suggest QA take a very close look at the entire getting started document and highlight all errors / inconsistencies.
Confirmed the "complete list" hyper-links in the document are pointing to a missing SVN reference
Who's responsible for updating the getting started document? Do we have time for a translation pass?
Fixed in change 22102. Since this bug seemed to have gotten dropped, I updated the URLs in all the affected documents, which was most of them (but not Hebrew, but I can't read it so I'm not sure why). This particular change doesn't need localization since it was just a wrong URL. I've also added a review of the Getting Started to the test procedure for all future releases of SC.
But when 7.1 is released (and presumably tagged in svn), the links for that release really should point to the 7.1/tags/... location, right?
Verified fixed in 7.1-22103
Ugh, I did that for a reason. I will revert this change. The reason is that the Changelog in 7.1 trunk may change after release, so users will see the wrong list of changes. Linking to the official 7.1 tag is the right thing to do. You just have to know that it won't exist until we're done with the release.
This bug has now been fixed in the 7.1 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Reduce number of active targets for SC