<div dir="ltr">Hi,<div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 25, 2013 at 6:01 AM, Philippe Blouin <span dir="ltr"><<a href="mailto:philippe.blouin@inlibro.com" target="_blank">philippe.blouin@inlibro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div class="im"><blockquote type="cite"><div><span>I hope everyone
understands that a new default theme would *only* affect new
installations, and that the old themes would continue to be
maintained and available until the agreed deprecation time. </span><br>
<span></span><br>
<span>We have worked with two available themes for a while now.
We can work with three for as long as necessary. I just hope
it not necessary for long. </span><br>
<span></span><span></span></div>
</blockquote></div>
That's the thing, I got fixes in the pipeline that only modify the
/prog/ path. Will I need to redo them all for the other path? How
has the RM been managing these situations in 3.13->3.14 ?<br></div></blockquote><div><br></div><div>Thus far I have been writing and pushing follow-ups patches in cases where it was obvious how a patch written for prog should be applied to the Bootstrap theme. If a patch is too complicated to do that, most of the time I will push the prog patch and open a bug for the corresponding change to be made for Bootstrap. However, I anticipate that during the 3.16 cycle there may be cases where a major piece of functionality added to prog may need to be held back until a Bootstrap implementation is available, although I will assist in minimizing the number of times that happens.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
And for the future, if I hear that bootstrap is THE solution, we'll
code only for it, and offer only bootstrapt fixes for the master.
Mind you, I don't even know how different is bootstrap code from
/prog/, but a +20% in dev time + doubling the testing time (very
rough estimate) to get two paths out can kill our community budget,
so maintaining two versions it probably out of our reach for us.<br></div></blockquote><div><br></div><div>For new work, I recommend coding for Bootstrap first.</div></div><div class="gmail_extra"><br></div>Regards,</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Galen<br>--<br><div dir="ltr"><div>Galen Charlton</div><div>Manager of Implementation</div><div>Equinox Software, Inc. / The Open Source Experts</div><div>email: <a href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a></div>
<div>direct: +1 770-709-5581</div><div>cell: +1 404-984-4366</div><div>skype: gmcharlt</div><div>web: <a href="http://www.esilibrary.com/" target="_blank">http://www.esilibrary.com/</a></div><div>Supporting Koha and Evergreen: <a href="http://koha-community.org" target="_blank">http://koha-community.org</a> & <a href="http://evergreen-ils.org" target="_blank">http://evergreen-ils.org</a></div>
</div>
</div></div>