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 class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; ">of 'let the dates slip, the release will be better' seems to show pretty</span><span class="Apple-style-span" style="border-collapse: collapse; "> </span></font><span class="Apple-style-span" style="font-family: arial, sans-serif; ">decisivly that frequent releases with what's ready at that time work </span><span class="Apple-style-span" style="font-family: arial, sans-serif; ">better in practice than delaying a release until the features that were </span><span class="Apple-style-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 class="Apple-style-span" face="arial, sans-serif"><i>if you delay a release until the feature is ready, there is a lot of </i></font><span class="Apple-style-span" style="font-family: arial, sans-serif; "><i>preasure to declare it ready when it really isn't, because people really </i></span><span class="Apple-style-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 class="Apple-style-span" face="arial, sans-serif"><i>because the releases aren't predictable, developers really want thir stuff </i></font><span class="Apple-style-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 class="Apple-style-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 class="Apple-style-span" style="font-family: arial, sans-serif; "><i>when the next release will happen (and therefor when the code will be </i></span><span class="Apple-style-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><div class="gmail_quote">Lori Ayre</div></div>