<p><blockquote type="cite">On 21 Nov 2010 10:04, "Lori Bowen Ayre" <<a href="mailto:lori.ayre@galecia.com">lori.ayre@galecia.com</a>> wrote:<br><br>I want to pull out these paragraphs from David Lang's email because I think it is an important point about the benefits of sticking to time-based releases. I think if we had stuck to this principle, we wouldn't be having the troubles we are having (as a community) with some of our biggest contributors needing to support versions of Koha that are different from the latest official version. <div>
<br></div><div><div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<i>Several years of time based releases after many years <font face="arial, sans-serif"><span style="border-collapse:collapse">of 'let the dates slip, the release will be better' seems to show pretty</span><span style="border-collapse:collapse"> </span></font><span style="font-family:arial, sans-serif">decisivly that frequent releases with what's ready at that time work </span><span style="font-family:arial, sans-serif">better in practice than delaying a release until the features that were </span><span style="font-family:arial, sans-serif">tagged for it are all ready.</span></i></blockquote>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<i><br></i></blockquote><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<font face="arial, sans-serif"><i>if you delay a release until the feature is ready, there is a lot of </i></font><span style="font-family:arial, sans-serif"><i>preasure to declare it ready when it really isn't, because people really </i></span><span style="font-family:arial, sans-serif"><i>want all the other features that are in a new release.</i></span></blockquote>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<i><br></i></blockquote><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<font face="arial, sans-serif"><i>because the releases aren't predictable, developers really want thir stuff </i></font><span style="font-family:arial, sans-serif"><i>to go into _this_ release because they don't know how long they will have </i></span><span style="font-family:arial, sans-serif"><i>to wait for the next one. If you have frequent releases, the knowledge of </i></span><span style="font-family:arial, sans-serif"><i>when the next release will happen (and therefor when the code will be </i></span><span style="font-family:arial, sans-serif"><i>upstream)</i></span></blockquote>
<br><div class="gmail_quote">Well said, David. And here here! And ++</div></div><div class="gmail_quote"><br></div><font color="#888888"><div class="gmail_quote">Lori Ayre</div></font></div>
<br>_______________________________________________<br>
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br></blockquote></p>