<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The Feedback Loop : Connect 2.2</title><link>http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx</link><description>Tags: Connect 2.2</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Connect 2.2 QFE 1 Deployed</title><link>http://blogs.msdn.com/csnow/archive/2006/11/01/connect-2-2-qfe-1-deployed.aspx</link><pubDate>Wed, 01 Nov 2006 23:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:926857</guid><dc:creator>Cyclometh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/csnow/comments/926857.aspx</comments><wfw:commentRss>http://blogs.msdn.com/csnow/commentrss.aspx?PostID=926857</wfw:commentRss><description>&lt;P&gt;It went up yesterday- thanks for your patience, especially you Vista testers, who bore the brunt of the display issues. We're already hard at work on Connect 2.3, and I'll provide more data on that as we move forward and solidify things.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=926857" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx">Connect 2.2</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect/default.aspx">Connect</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Vista/default.aspx">Vista</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Site+Notifications/default.aspx">Site Notifications</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Release/default.aspx">Release</category></item><item><title>First post-2.2 fixes coming</title><link>http://blogs.msdn.com/csnow/archive/2006/10/30/first-post-2-2-fixes-coming.aspx</link><pubDate>Mon, 30 Oct 2006 20:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:903931</guid><dc:creator>Cyclometh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/csnow/comments/903931.aspx</comments><wfw:commentRss>http://blogs.msdn.com/csnow/commentrss.aspx?PostID=903931</wfw:commentRss><description>&lt;P&gt;We had a pretty good Connect 2.2 deployment, although it took a little longer than we expected. We've identified what caused that and it shouldn't occur again. We've got our Release Manager working on a mechanism for zero-downtime deployments of Connect as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Some issues were identified pretty quickly, in particular with the Vista/Longhorn beta. Because the Vista beta receives bugs via the MBC, users are not allowed to submit feedback directly via Connect. This resulted in the Feedback overview page showing the text "Sign in to view..." for your watchlist and "Posted By Me" bugs even when signed in. We've got a fix for this in testing, along with some late-breaking localization issues and a couple of UI tweaks (mostly for localization support).&lt;/P&gt;
&lt;P&gt;The current&amp;nbsp;plan for the update is early this week. I posted in the Vista newsgroups on the Microsoft beta newsgroups with links that will allow you to access your posted items, watchlist, and newest bugs with one click:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Please note that the following URLs are specific to the Vista beta. If you're not a member of the Vista beta, these links will not work for you. These links will require you to sign in.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;(you can use the same&amp;nbsp;pattern on other sites, though).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To access all of your bugs:&lt;BR&gt;&lt;BR&gt;&lt;A href="mhtml:{277ACA95-7941-45B7-9028-CA03ED72A3BA}mid://00001075/!x-usc:https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=1"&gt;https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=1&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;To access all bugs on your watch list:&lt;BR&gt;&lt;BR&gt;&lt;A href="mhtml:{277ACA95-7941-45B7-9028-CA03ED72A3BA}mid://00001075/!x-usc:https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=3"&gt;https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=3&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;For the top-rated bugs:&lt;BR&gt;&lt;BR&gt;&lt;A href="mhtml:{277ACA95-7941-45B7-9028-CA03ED72A3BA}mid://00001075/!x-usc:https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=4"&gt;https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=4&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;For the top-rated suggestions:&lt;BR&gt;&lt;BR&gt;&lt;A href="mhtml:{277ACA95-7941-45B7-9028-CA03ED72A3BA}mid://00001075/!x-usc:https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=5"&gt;https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=5&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;For all bugs posted by your organization (only applicable if you're a member &lt;BR&gt;of an organization):&lt;BR&gt;&lt;BR&gt;&lt;A href="mhtml:{277ACA95-7941-45B7-9028-CA03ED72A3BA}mid://00001075/!x-usc:https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=2"&gt;https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=2&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;For the newest bugs:&lt;BR&gt;&lt;BR&gt;&lt;A href="mhtml:{277ACA95-7941-45B7-9028-CA03ED72A3BA}mid://00001075/!x-usc:https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=6"&gt;https://connect.microsoft.com/Windows/feedback/searchresults.aspx?FeedbackOverviewType=6&lt;/A&gt;&lt;BR&gt;&lt;BR&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=903931" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx">Connect 2.2</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect/default.aspx">Connect</category><category domain="http://blogs.msdn.com/csnow/archive/tags/bugs/default.aspx">bugs</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Deployment/default.aspx">Deployment</category></item><item><title>Connect 2.2 Deployment</title><link>http://blogs.msdn.com/csnow/archive/2006/10/26/connect-2-2-deployment.aspx</link><pubDate>Fri, 27 Oct 2006 00:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:877418</guid><dc:creator>Cyclometh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/csnow/comments/877418.aspx</comments><wfw:commentRss>http://blogs.msdn.com/csnow/commentrss.aspx?PostID=877418</wfw:commentRss><description>&lt;P&gt;Connect 2.2 is being deployed as I write this, as you may have noticed from the "Site Maintenance" page. However, a snag was hit during the upgrade which forced us to restart a process, and we're going to be longer than the original timeframe. We're hoping to have things up and running within the next couple of hours.&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=877418" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx">Connect 2.2</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect/default.aspx">Connect</category></item><item><title>Connect 2.2 Feedback</title><link>http://blogs.msdn.com/csnow/archive/2006/10/12/connect-2-2-feedback.aspx</link><pubDate>Thu, 12 Oct 2006 20:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:820289</guid><dc:creator>Cyclometh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/csnow/comments/820289.aspx</comments><wfw:commentRss>http://blogs.msdn.com/csnow/commentrss.aspx?PostID=820289</wfw:commentRss><description>&lt;P&gt;For those of you that have taken the time to look at Connect 2.2 on the ConnectBeta site, thanks! &lt;/P&gt;
&lt;P&gt;Connect 2.2 is in lockdown at the moment, which means we don't make any changes that we don't consider&amp;nbsp;absolutely necessary for the site to function. This is a critical phase of stabilization, because we&amp;nbsp;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.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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 &lt;A class="" href="http://connect.microsoft.com/Connect/feedback/ViewFeedback.aspx?FeedbackID=224394" mce_href="http://connect.microsoft.com/Connect/feedback/ViewFeedback.aspx?FeedbackID=224394"&gt;this bug&lt;/A&gt;&amp;nbsp;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).&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;I'd encourage others to take a look at the Connect 2.2 site on &lt;A href="http://connectbeta.microsoft.com/"&gt;http://connectbeta.microsoft.com&lt;/A&gt;. If you find bugs, please file them on the live Connect site at &lt;A href="http://connect.microsoft.com/Connect/Feedback"&gt;http://connect.microsoft.com/Connect/Feedback&lt;/A&gt;. 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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;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!&lt;/P&gt;
&lt;P&gt;Some issues identified by the Connect beta site I'd like to answer here:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;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.&lt;/LI&gt;
&lt;LI&gt;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".&lt;/LI&gt;
&lt;LI&gt;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.&lt;/LI&gt;
&lt;LI&gt;The display issue with "post a comment to Microsoft" has been corrected, as above.&lt;/LI&gt;&lt;/UL&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=820289" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/csnow/archive/tags/Feedback/default.aspx">Feedback</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx">Connect 2.2</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Beta/default.aspx">Beta</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+Beta/default.aspx">Connect Beta</category></item><item><title>Connect 2.2 Preview</title><link>http://blogs.msdn.com/csnow/archive/2006/10/11/connect-2-2-preview.aspx</link><pubDate>Wed, 11 Oct 2006 23:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:817520</guid><dc:creator>Cyclometh</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/csnow/comments/817520.aspx</comments><wfw:commentRss>http://blogs.msdn.com/csnow/commentrss.aspx?PostID=817520</wfw:commentRss><description>&lt;P&gt;Is finally &lt;A class="" href="https://connectbeta.microsoft.com/site/sitehome.aspx?SiteID=3" mce_href="https://connectbeta.microsoft.com/site/sitehome.aspx?SiteID=3"&gt;here&lt;/A&gt;! Go to &lt;A href="https://connectbeta.microsoft.com/site/sitehome.aspx?SiteID=3"&gt;https://connectbeta.microsoft.com/site/sitehome.aspx?SiteID=3&lt;/A&gt;&amp;nbsp;and take a look around. You can do most of the things you can on the main Connect site, although you'll find that the available programs list is pretty limited. None of the feedback or sites from the production site are available here, with the exception of the Connect demo site.&lt;/P&gt;
&lt;P&gt;Please take&amp;nbsp;a look around and see what you think. After you sign in, click the "Manage My Profile" link at the bottom and fill out your profile data in order to be able to submit feedback. Keep in mind that this is a beta site, so the feedback isn't going to be processed or resolved. Don't enter your real bugs here- or do, but enter them on the real Connect site as well!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;After you've taken a look around, if you have any comments you can file a feedback or suggestion form on the main Connect site at &lt;A href="http://connect.microsoft.com/Connect/Feedback"&gt;http://connect.microsoft.com/Connect/Feedback&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;A couple of notes about the beta site; some issues were found after the deployment to the beta site and have already been resolved internally.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;File uploads may not work correctly with Firefox 1.5. This is known and has been corrected in a later internal build.&lt;/LI&gt;
&lt;LI&gt;Feedback should work with both Opera and Firefox, although some display elements may not be correctly placed or visible in non-IE browsers. These issues have been largely eliminated in our internal builds.&lt;/LI&gt;
&lt;LI&gt;After attaching files, you may notice that the "attached files count" on the Feedback Details page always remains 0. This has been corrected in our latest builds.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;I look forward to hearing what you think.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=817520" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/csnow/archive/tags/Feedback/default.aspx">Feedback</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx">Connect 2.2</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect/default.aspx">Connect</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Beta/default.aspx">Beta</category></item><item><title>Preview Update</title><link>http://blogs.msdn.com/csnow/archive/2006/10/09/Preview-Update.aspx</link><pubDate>Mon, 09 Oct 2006 20:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:808761</guid><dc:creator>Cyclometh</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/csnow/comments/808761.aspx</comments><wfw:commentRss>http://blogs.msdn.com/csnow/commentrss.aspx?PostID=808761</wfw:commentRss><description>&lt;P&gt;Hey folks- sorry I didn't come through on the details of the 2.2 preview. We had some UX changes to implement and those kept me pretty busy the last few days. On the plus side, the new changes look great and hopefully we can get them in front of you folks pretty soon on the Connect beta site. I'll post some screenshots as well- I think you'll be pleased.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Connect 2.2, currently slated for deployment at the end of October or early November, is primarily a bug fix and stabilization release. We deliberately decided not to take on new feature work in this release- there are some new features, but they're not major ones and there's not many- and focus exclusively on bug fixes, performance improvements, and stabilization. In terms of look and feel, you'll find a number of significant changes in the Feedback area, and in terms of performance, we've made some serious improvements- especially in searching feedback, a primary pain point for Connect.&lt;/P&gt;
&lt;P&gt;Moving forward, we're going to be continuing to stabilize and begin getting some new features into play. I have some pretty exciting ones on my plate for the Feedback area, and I'm looking forward to being able to share them with you.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=808761" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/csnow/archive/tags/Feedback/default.aspx">Feedback</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect+2.2/default.aspx">Connect 2.2</category><category domain="http://blogs.msdn.com/csnow/archive/tags/Connect/default.aspx">Connect</category></item></channel></rss>