<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi,<br>
<br>
Your arguments are actually supporting more the time-based cycles
:). Keep in mind that all the time a new release will be a set of
new features, so basically all releases are also featured driven.
But to make it more predictable, we consider some time limits (for
a release cycle) - limits are quite large 5 to 7 months, so we
have flexibility to fit various sets of features in that interval.
The main idea with time-based cycles is to try to control how long
will take for have the next release (more predictable, without
large gaps between releases) and also to speed up the features
delivery (having a faster cycle, features will be available in
stable versions quicker).<br>
<br>
Let me know if I missed some your points or if my thinking is
wrong.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 11/26/2012 04:02 PM, Jeff Pyle wrote:
<blockquote
cite="mid:CACYJG3J1MQ6m=PCgu7JtzXr3q8e662g6mcX1-cB8CNiMU5z4+A@mail.gmail.com"
type="cite">
<div>On Sun, Nov 25, 2012 at 10:32 AM, Brett Nemeroff <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a>></span>
wrote:</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="gmail_quote">
<div class="im">
<div><br>
</div>
</div>
<div> Just my two cents here...</div>
<div><br>
</div>
<div>With regards to the release cycle... I typically find
myself doing "production" deployments for my clients. What
I need is a stable version. And then hotfixes as bugs are
discovered. </div>
<div><br>
</div>
<div>I prefer feature driven releases because I can look
forward to when feature X will be available. My production
deployments typically run untouched while in production
mode. Upgrades occur when new features are needed AND
available in stable builds. I don't typically upgrade
simply because an upgrade is available. Of course, I'll
normally upgrade for critical fixes or security fixes
(which I'd see as a hotfix typically and not a full
release)</div>
<div><br>
</div>
<div>If I knew a release was going to be available on a
particular date, I would without question start reviewing
that release and it's new capabilities; but I wouldn't
need it for a production build. </div>
<div><br>
</div>
<div>If I knew a feature was available on a certain date, I
could pitch that to my clients if it was a feature they
might need. Also, I'm afraid that time based releases may
rush features out before they are ready.</div>
<div><br>
</div>
<div>That's just my perspective based on my workflow. I'm
sure there are others that feel differently. :)</div>
<span class="HOEnZb"><font color="#888888">
<div>-Brett</div>
</font></span></div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>I, for one, share Brett's perspective.</div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>