Connect 2.2 Feedback
For those of you that have taken the time to look at Connect 2.2 on the ConnectBeta site, thanks!
Connect 2.2 is in lockdown at the moment, which means we don't make any changes that we don't consider absolutely necessary for the site to function. This is a critical phase of stabilization, because we have to reduce code churn as much as we possibly can. That means the bar is set pretty high for bug fixes to make it into Connect 2.2.
However, at least one person has filed a bug on the Connect Product Improvement site, which we just fixed for Connect 2.2. Thanks go out to AlconicCF, who filed this bug on the Connect Product Improvement site against Connect 2.2. The problem was primarily a display one; when the first comment is added by the feedback author, the region that shows them wasn't being updated to be visible. If you refresh the page, the comment is added again. The workaround was to go back to the overview page and come back to the feedback item (ugh).
Since the fix was pretty minor and the bug severe enough (customer experience issues are given a lot of weight), we triaged and fixed it this morning.
I'd encourage others to take a look at the Connect 2.2 site on http://connectbeta.microsoft.com. If you find bugs, please file them on the live Connect site at http://connect.microsoft.com/Connect/Feedback. At this point, the bar is set very high, and only what we would call "ship-blocking" bugs will be considered for implementation in 2.2.
I'd still like you to file any bugs, even minor ones and nits, if you find them. That way we can get them in the pipeline for hotfix releases or another point release, or assess them for fix in a major release. Your feedback is valuable to us!
Some issues identified by the Connect beta site I'd like to answer here:
- Comments are not searchable in Connect 2.2. We're going to be working on making comments, vote text, validations, workarounds, and all other data associated with a feedback item searchable in the future.
- Feedback search doesn't do a lot of stemming in the search, and generally relies on exact matches- ie, you won't find "software" if you enter "softwares". You can use an asterisk as a wildcard for searching words- i.e., "soft* would find both "software" and "softwares".
- The index may lag a few minutes behind when you entered your feedback. Generally we don't think this will occur often on the production site, as the hardware used there is much more powerful and should be able to keep up. However, at times feedback submissions are very heavy, and in times like that the search index may take time to snarf up your submission.
- The display issue with "post a comment to Microsoft" has been corrected, as above.
