Hello.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Well, if no-one fix anything on this version, what will be the<br>
difference between orphan and killed ?<br>
I think as long as there is no RMaint for 3.4, it&#39;s EOL, whatever we can<br>
decide ! if someone want to keep it updated, then apply to be 3.4 RMaint !<br>
</blockquote>
<br></div>
Yes, effectively EOL is EOL regardless of what we name it. However, the naming difference does distinguish our attitude towards it. &#39;Orphaned&#39; would mean we can expect people to still be using it. It&#39;s for stragglers who haven&#39;t caught up version-wise. &#39;Killed&#39; means we don&#39;t want people using that version anymore. We won&#39;t support them. They should have upgraded by now. A much harsher attitude.<br>
</blockquote><div><br></div><div>If Koha 3.4 is working for a library, by all means they should continue using it (but upgrade to the latest 3.4.x version, since there were some security issues that were fixed!). However, if someone wants support from me, they need to use a version of Koha that is recent enough that I remember  how it works. So I don&#39;t really see a difference between &quot;killed&quot; and &quot;orphaned.&quot;</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What does that mean for Koha Developers? Nothing, &quot;Orphaned&quot; = &quot;Killed&quot; = &quot;EOL&quot;. They&#39;ll be spending their time on the latest stable releases (eg. 3.8.3 and 3.6.7). What does it mean for Koha Users? They don&#39;t have to feel locked in, because of our 6 month release schedule. They have a year breathing room. It will cost half as much annually to upgrade, because they&#39;ll be slack and upgrade every two years (unless a major bug comes along and they don&#39;t have the budget to get it fixed). </blockquote>
<div> </div><div>Why don&#39;t we just say &quot;3.4.x is End of Life and no longer supported&quot; and leave it at that? Killed or orphaned, I&#39;m not taking up RMaint duties for that branch, and as the RMaint for 3.6.x I think I&#39;d probably be considered the most likely candidate for that position, in the absence of anyone who actually wants to spend time on maintaining the 3.4.x branch. When someone asks for help with 3.4.x, or even 3.6.0 on #koha, we will always recommend they upgrade to a more recent version, because that&#39;s just good practice. We fix lots of bugs every month.</div>
<div><br></div><div>Regards,</div><div>Jared</div><div><br></div></div>-- <br>Jared Camins-Esakov<div>Bibliographer, C &amp; P Bibliography Services, LLC</div><div>(phone) +1 (917) 727-3445</div><div>(e-mail) <a href="mailto:jcamins@cpbibliography.com" target="_blank">jcamins@cpbibliography.com</a></div>
<div>(web) <a href="http://www.cpbibliography.com/" target="_blank">http://www.cpbibliography.com/</a></div><br>