{"id":11845,"date":"2016-04-28T13:47:29","date_gmt":"2016-04-28T18:47:29","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/?p=11845"},"modified":"2019-02-16T22:46:19","modified_gmt":"2019-02-16T22:46:19","slug":"update-on-tfs-2015-update-2-1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/update-on-tfs-2015-update-2-1\/","title":{"rendered":"Update on TFS 2015 Update 2.1"},"content":{"rendered":"

Hmm, it’s been a few days of reflection.\u00a0 I don’t think I expected my post on the bugs we were fixing in Update 2.1 to generate so many comments about other bugs that people are hitting.\u00a0 Let me share some questions that have been on my mind and my thoughts on them…\nWhy did I get so many bugs reported as comments on my blog?<\/strong>\nIn the end, my blog isn’t the place I want people reporting bugs.\u00a0 It’s high cost for me (I’m just overhead because I route them to the right person to look at them).\u00a0 It’s not a great experience for you – you don’t have a great way to track updates.\u00a0 And it’s not a great experience for our engineers because getting additional details is difficult – blog comments often don’t have contact info.\u00a0 The system we have for this is http:\/\/connect.microsoft.com for bugs and http:\/\/visualstudio.uservoice.com for suggestions.\nI have some hypotheses.\u00a0 1) I kinda asked for it by putting up a post with a lot of bugs.\u00a0 2) My blog is REALLY responsive.\u00a0 If you post something there, I almost always read it within an hour and forward it to someone on my team and, because it comes from their VP, they tend to drop whatever they are doing and get right on it.\u00a0 So that part of the experience for you can’t be beat.\u00a0 2) connect.microsoft.com is a less than ideal (to be gentle) experience both in terms of the UX and, I think, our responsiveness.\nBut those are just my hypotheses.\u00a0 I’m interested in any thoughts you all have on this.\nDon’t get me wrong, my blog is definitely available for anyone who feels they need to be heard.\u00a0 If you are frustrated about something and can’t get satisfaction (or really happy about something and just want to say so), I’m here.\u00a0 I don’t want people to ever feel like I’m discouraging discussion.\u00a0 At the same time, I’d like for people to find satisfaction in our “normal” channels.\u00a0 If they aren’t working, I want to know why and see what it takes to fix them.\nI’ve asked someone to take all the bugs reported on my blog since Update 2 shipped and go look on connect.microsoft.com and see if they are there.\u00a0 Maybe they got filed and we just ignored them.\u00a0 If so, that’s something to fix.\nWith this additional list of bugs, what do I do with Update 2.1?<\/strong>\nThe schedule for the final checkin for Update 2.1 is today.\u00a0 We’re not going to repro, identify and fix every one of them by then (and I’m still seeing a couple of new ones a day).\u00a0 I’ve decided we’re going to go ahead and ship Update 2.1 “on schedule” with the fixes we have.\u00a0 Regardless of however many additional fixes we could make, Update 2.1 has a couple of dozen valuable improvements.\u00a0 Further Update 3 isn’t that\u00a0<\/em>far away.\u00a0 If I wait too long, Update 2.1 becomes pointless.\u00a0 We’ll finish “development” on Update 3 in about 6 weeks and ship it within a few weeks after that (I think).\u00a0 Given all that, we are going to move forward and ship Update 2.1 next week.\nWhat am I going to do with the bugs that have been reported?<\/strong>\nWe’re going to continue to work on them.\u00a0 Not only that, I’ve asked the team to go back and do a thorough scrub of connect.microsoft.com, Send-a-smile feedback, etc. and identify all the other bug reports that should be and can be fixed for Update 3.\u00a0 So, keep reporting any bugs you find.\u00a0 I can’t promise that we will fix all of them but we’ll fix as many as we can.\nWhat does this all mean about the quality of our development process?<\/strong>\nWell, I’m not sure yet.\u00a0 It’s the first time we’ve ever wanted to do a .1 release on an Update.\u00a0 We’ve had bugs.\u00a0 There are always bugs.\u00a0 It’s nigh impossible to eliminate every single bug in a very large complex system.\u00a0 But, it’s the first time we’ve had enough of them that we’ve said, hmm, this isn’t good enough.\u00a0 We need to do better.\u00a0 We’re also doing a retrospective on all the bugs that have been reported to understand when they were introduced, what the root cause was, what could have been done to have detected them earlier, etc.\u00a0 From that we’ll make some adjustments and I hope we will not have this number of bugs again any time soon.\nAll that said, I’m not saying Update 2 was a *bad* release.\u00a0 Lots of people have installed it and lots are using it very happily.\u00a0 It has lots of good stuff in it that people are very happy about.\u00a0 But, it could have and should have been a *better* release.\u00a0 Once I’ve seen the retrospective, I’ll know more.\u00a0 Overall I am very happy with and proud of the work this team does, the quality and commitment of the people and the innovation in the process that allows us to deliver so much value in so many different ways.\u00a0 At the same time, everything is an opportunity to learn more and be better.\u00a0 The only question is whether or not you recognize the opportunity and act on it.\nBrian<\/p>\n","protected":false},"excerpt":{"rendered":"

Hmm, it’s been a few days of reflection.\u00a0 I don’t think I expected my post on the bugs we were fixing in Update 2.1 to generate so many comments about other bugs that people are hitting.\u00a0 Let me share some questions that have been on my mind and my thoughts on them… Why did I […]<\/p>\n","protected":false},"author":244,"featured_media":14617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5],"class_list":["post-11845","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-tfs"],"acf":[],"blog_post_summary":"

Hmm, it’s been a few days of reflection.\u00a0 I don’t think I expected my post on the bugs we were fixing in Update 2.1 to generate so many comments about other bugs that people are hitting.\u00a0 Let me share some questions that have been on my mind and my thoughts on them… Why did I […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/11845","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/users\/244"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/comments?post=11845"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/posts\/11845\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media\/14617"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/media?parent=11845"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/categories?post=11845"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/bharry\/wp-json\/wp\/v2\/tags?post=11845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}