<?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>Read about Rosario</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx</link><description>As we announced last month, the version of Team System that we're working on after Team System "Orcas" is known as "Rosario". While the details aren't locked down yet, we've made exciting progress towards making this release real. We've definitely been</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Read about Rosario</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx#2276033</link><pubDate>Wed, 25 Apr 2007 23:49:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2276033</guid><dc:creator>Stuart Ballard</dc:creator><description>&lt;p&gt;One thing I really miss in Whidbey Team System is the ability for check in notification emails (those wonderful TFSAlert things) to actually include the text of the changes made. I've seen this in a lot of open source projects and it's an excellent tool for code review; I think it's doubly so in small teams such as the one I work for. TF clearly supports the ability to do code review pre-checkin, but doing it post-checkin makes a lot more sense for small teams who can't afford to require two developers blocked in order to check one change in.&lt;/p&gt;
&lt;p&gt;I like knowing about every checkin and often I am able to provide useful feedback for my teammates based on the email I do get - and vice versa - but I've missed issues that would have been blatantly obvious if the actual code changes were visible to me in the email.&lt;/p&gt;
&lt;p&gt;Right now even the links in the email don't give me any ability to see what actually changed, without firing up VS and doing a diff operation by hand. Never going to happen. And hence a valuable opportunity for code review gets missed...&lt;/p&gt;
</description></item><item><title>re: Read about Rosario</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx#2281856</link><pubDate>Thu, 26 Apr 2007 08:57:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2281856</guid><dc:creator>Tanveer Badar</dc:creator><description>&lt;p&gt;This also means that since Orcas is further away from Whidbey Island, Visual Studio 2007 will have more features than Visual Studio 2005.&lt;/p&gt;
&lt;p&gt;But as Rosario is on Orcas Island, it will only build on Orcas but will not have that many new features apart from product stabilization and bug fixes.&lt;/p&gt;
&lt;p&gt;Am I incorrect?&lt;/p&gt;
</description></item><item><title>re: Read about Rosario</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx#2285429</link><pubDate>Thu, 26 Apr 2007 14:23:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2285429</guid><dc:creator>jeffbe</dc:creator><description>&lt;p&gt;Stuart - thanks for your suggestion regarding checkin notification emails. &amp;nbsp;I very much like your idea and have passed it on to the version control team. &amp;nbsp;If you have additional product ideas, please don't hesitate to send them to us via Connect: &amp;nbsp;&lt;a rel="nofollow" target="_new" href="https://connect.microsoft.com/VisualStudio"&gt;https://connect.microsoft.com/VisualStudio&lt;/a&gt;. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
</description></item><item><title>re: Read about Rosario</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx#2285473</link><pubDate>Thu, 26 Apr 2007 14:28:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2285473</guid><dc:creator>jeffbe</dc:creator><description>&lt;p&gt;Tanveer - we expect Rosario will have many new features for the Team System specific components but to keep the other Visual Studio components pretty much as is (with perhaps some bug fixes). &amp;nbsp;So, following the analogy (which certainly isn't perfect by the way) while Rosario is certainly on Orcas Island, it's got ammenities you can't find anywhere else. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Make sense?&lt;/p&gt;
</description></item><item><title>Tracking Team System</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx#3826092</link><pubDate>Thu, 12 Jul 2007 09:10:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3826092</guid><dc:creator>Rob Caron</dc:creator><description>&lt;p&gt;If you haven't realized it by now, my blog isn't tracking Team System as closely as it once did. If you're&lt;/p&gt;
</description></item><item><title>Ecco dove dobbiamo andare ad Aprile... :-D</title><link>http://blogs.msdn.com/jeffbe/archive/2007/04/25/read-about-rosario.aspx#6711634</link><pubDate>Sun, 09 Dec 2007 12:48:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6711634</guid><dc:creator>Normal people bore me!</dc:creator><description>&lt;p&gt;Ecco dove dobbiamo andare ad Aprile... :-D&lt;/p&gt;
</description></item></channel></rss>