<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: On the Release Train</title>
	<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/</link>
	<description>Ignite Realtime</description>
	<pubDate>Sun, 12 Oct 2008 11:34:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: The Release Train at Jive Talks</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-22932</link>
		<pubDate>Thu, 02 Aug 2007 00:18:51 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-22932</guid>
					<description>[...] Back in April, I blogged about how we were adopting a release train model for our Open Source projects. Since then, we've rolled out the same process to our commercial products Clearspace and Jive Forums. The release train is a fairly fundamental departure from how we've done releases in the past, so we wanted to provide more details about exactly how it works. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Back in April, I blogged about how we were adopting a release train model for our Open Source projects. Since then, we&#8217;ve rolled out the same process to our commercial products Clearspace and Jive Forums. The release train is a fairly fundamental departure from how we&#8217;ve done releases in the past, so we wanted to provide more details about exactly how it works. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: user_with_brain</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-20096</link>
		<pubDate>Wed, 04 Jul 2007 20:43:09 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-20096</guid>
					<description>Hello,

i tried Sparks. Looks fine. But 75MB for roster and one chat? ROFL! Hire some stuff for real programing and use brain! Do you use own product? Or your standard is 4GB RAM? I'm glad you program "just" IM :)

Why don't you help to make better Gajim, PSI or other good programs, insted of tons of code ended with useless SW? Nice pictures and skins are the last, first you need program.

Try google to find some basics about memory management and Jabber clients ;)</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>i tried Sparks. Looks fine. But 75MB for roster and one chat? ROFL! Hire some stuff for real programing and use brain! Do you use own product? Or your standard is 4GB RAM? I&#8217;m glad you program &#8220;just&#8221; IM <img src='http://www.igniterealtime.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Why don&#8217;t you help to make better Gajim, PSI or other good programs, insted of tons of code ended with useless SW? Nice pictures and skins are the last, first you need program.</p>
<p>Try google to find some basics about memory management and Jabber clients <img src='http://www.igniterealtime.org/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Sam</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-18569</link>
		<pubDate>Mon, 18 Jun 2007 23:05:26 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-18569</guid>
					<description>This sounds like _classic_ waterfall process, only with fewer stages in the pipeline and using Scrum to encapsulate the missing pieces.  We use something similar for the company I work at, but I'm not happy with it.  We have a _weekly_ release cycle here, which compounds the problems.  QA's builds are usually quite out of synch with the dev-team's builds.  Finding bugs introduces "bubbles" into the pipeline which delays the release train.

I think it'd be much better to use an extreme programming-style development model.  That is, each iteration, estimate what goes into the product and work to make it a reality.  Things which do not make it in (including partially implemented features) are _dropped_ in favor of maintaining the scheduled release date.  Dropped features are deferred for the subsequent iteration's planning session.  This may take longer to "finish" the product, but the goods are always on time and of very high quality.</description>
		<content:encoded><![CDATA[<p>This sounds like _classic_ waterfall process, only with fewer stages in the pipeline and using Scrum to encapsulate the missing pieces.  We use something similar for the company I work at, but I&#8217;m not happy with it.  We have a _weekly_ release cycle here, which compounds the problems.  QA&#8217;s builds are usually quite out of synch with the dev-team&#8217;s builds.  Finding bugs introduces &#8220;bubbles&#8221; into the pipeline which delays the release train.</p>
<p>I think it&#8217;d be much better to use an extreme programming-style development model.  That is, each iteration, estimate what goes into the product and work to make it a reality.  Things which do not make it in (including partially implemented features) are _dropped_ in favor of maintaining the scheduled release date.  Dropped features are deferred for the subsequent iteration&#8217;s planning session.  This may take longer to &#8220;finish&#8221; the product, but the goods are always on time and of very high quality.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Derek DeMoro</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-18271</link>
		<pubDate>Sun, 17 Jun 2007 01:22:14 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-18271</guid>
					<description>I actually wanted to comment on how things are going for me personally. I think the one BIG benefit of this is that it allows the engineer to stay very focused on the tasks at hand and to be less reactionary to feedback. I've talked with matt about this in depth and I think he would agree that when you take out some of the "free time" in development, the experimentation side of development just doesn't happen as much, and the quality does go up. However, my one complaint is that the creativity part of the job goes down just a bit. No longer can I change the color of a tab to lighter blue without it being approved for the release :( heh.</description>
		<content:encoded><![CDATA[<p>I actually wanted to comment on how things are going for me personally. I think the one BIG benefit of this is that it allows the engineer to stay very focused on the tasks at hand and to be less reactionary to feedback. I&#8217;ve talked with matt about this in depth and I think he would agree that when you take out some of the &#8220;free time&#8221; in development, the experimentation side of development just doesn&#8217;t happen as much, and the quality does go up. However, my one complaint is that the creativity part of the job goes down just a bit. No longer can I change the color of a tab to lighter blue without it being approved for the release <img src='http://www.igniterealtime.org/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  heh.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: james</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-18060</link>
		<pubDate>Fri, 15 Jun 2007 18:25:52 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-18060</guid>
					<description>Hey mods, nuke my last message the link didn't work.

Since you’re having problems with effectively estimating schedules and dynamically adjusting to changes, i would suggest checking out this webcast:

Skip to the end where he goes to talk about scheduling, it really wouldn’t matter if you’re using SOA or not.
MSDN Webcast: Applying Service-Orientation to Your Development Process (Level 300) (located here: http://www.microsoft.com/events/series/teched07.aspx?tab=webcasts&#38;id=21940)

the big point is knowing how far along in a given project you are by a binary method, not by asking the developer ‘how far along are you’. you’ll see in the video, he explains it way better than i could.</description>
		<content:encoded><![CDATA[<p>Hey mods, nuke my last message the link didn&#8217;t work.</p>
<p>Since you’re having problems with effectively estimating schedules and dynamically adjusting to changes, i would suggest checking out this webcast:</p>
<p>Skip to the end where he goes to talk about scheduling, it really wouldn’t matter if you’re using SOA or not.<br />
MSDN Webcast: Applying Service-Orientation to Your Development Process (Level 300) (located here: <a href="http://www.microsoft.com/events/series/teched07.aspx?tab=webcasts&amp;id=21940" rel="nofollow">http://www.microsoft.com/events/series/teched07.aspx?tab=webcasts&amp;id=21940</a>)</p>
<p>the big point is knowing how far along in a given project you are by a binary method, not by asking the developer ‘how far along are you’. you’ll see in the video, he explains it way better than i could.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: matt</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-15740</link>
		<pubDate>Mon, 04 Jun 2007 23:47:05 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-15740</guid>
					<description>Mark -- I completely agree. Any process that promises to fix everything is obviously BS. :) But, we're quite happy with what this set of limitations has given us so far. I'm planning to do a follow-up blog entry with more details on our progress in the not too distant future. One thing that's emerged already is timing big demos and massive happy hours for the end of each train. We had a total blow-out happy hour with an ice theme on Friday. Maybe I'll have to get some pictures up...</description>
		<content:encoded><![CDATA[<p>Mark &#8212; I completely agree. Any process that promises to fix everything is obviously BS. <img src='http://www.igniterealtime.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  But, we&#8217;re quite happy with what this set of limitations has given us so far. I&#8217;m planning to do a follow-up blog entry with more details on our progress in the not too distant future. One thing that&#8217;s emerged already is timing big demos and massive happy hours for the end of each train. We had a total blow-out happy hour with an ice theme on Friday. Maybe I&#8217;ll have to get some pictures up&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mark</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-15706</link>
		<pubDate>Mon, 04 Jun 2007 22:40:00 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-15706</guid>
					<description>I am suspicious of any software process that claims to make releases predictable.  Making release DATES predictable is easy, but -- now that you have had some time to try out this process -- are you finding that these releases are also high-quality and sufficiently feature-rich to justify the overhead (regression testing, upgrade support, etc.) of each new release?  Have you had to tweak the process yet?</description>
		<content:encoded><![CDATA[<p>I am suspicious of any software process that claims to make releases predictable.  Making release DATES predictable is easy, but &#8212; now that you have had some time to try out this process &#8212; are you finding that these releases are also high-quality and sufficiently feature-rich to justify the overhead (regression testing, upgrade support, etc.) of each new release?  Have you had to tweak the process yet?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Deniz</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-12444</link>
		<pubDate>Tue, 15 May 2007 06:17:14 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-12444</guid>
					<description>Hello, we have isa server 2004  and we are installing spark program 2.5.2 we can chating word but for voice we can't speaking what we do or what is voice port number 
i want permission voice on isa server2004 but i dont know how pls help we thank you</description>
		<content:encoded><![CDATA[<p>Hello, we have isa server 2004  and we are installing spark program 2.5.2 we can chating word but for voice we can&#8217;t speaking what we do or what is voice port number<br />
i want permission voice on isa server2004 but i dont know how pls help we thank you
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: matt</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-10273</link>
		<pubDate>Sun, 29 Apr 2007 14:27:57 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-10273</guid>
					<description>White Spy -- I also answered your question in your own blog entry. But to re-paste here: we do continuous integration on both trunk and the branch at the same time — that’s what "development" and "stable" are.</description>
		<content:encoded><![CDATA[<p>White Spy &#8212; I also answered your question in your own blog entry. But to re-paste here: we do continuous integration on both trunk and the branch at the same time — that’s what &#8220;development&#8221; and &#8220;stable&#8221; are.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: License 2 Code &#187; On the Release Train at Ignite Realtime</title>
		<link>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-10260</link>
		<pubDate>Sun, 29 Apr 2007 13:46:16 +0000</pubDate>
		<guid>http://www.igniterealtime.org/blog/2007/04/22/on-the-release-train/#comment-10260</guid>
					<description>[...] On the Release Train at Ignite Realtime [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] On the Release Train at Ignite Realtime [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
