Thanks Owen and Chris for your detailed answers. I'll have to read these later, but they look helpful.<br><br>I really didn't mean for my first question to be a challenge, it was a legitimate question. I know that Chris and Galen are smart guys. I even had the pleasure of working with Galen for a while.<br>
<br>I really am trying to learn and understand this process (as I've been doing for the last two years). <br><br>Vicki<br><br><div class="gmail_quote">On Wed, Jul 7, 2010 at 9:26 AM, Chris Nighswonger <span dir="ltr"><<a href="mailto:cnighswonger@foundations.edu">cnighswonger@foundations.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2010/7/7 <a href="mailto:vtl@scls.lib.wi.us">vtl@scls.lib.wi.us</a> <<a href="mailto:vtl@scls.lib.wi.us">vtl@scls.lib.wi.us</a>>:<br>
<div class="im">> Why are you rebasing the harley code into 3.2? It was my understanding that<br>
> PTFS knew it was too late for the code in harley to be included in 3.2, but<br>
> that it could be integrated properly into 3.4. That is why it was released<br>
> in its entirety for now rather than as patches.<br>
<br>
</div>Harley is not being rebased over "3.2". Rather it is being rebased<br>
over the current HEAD (the tip of the trunk so to speak) which also<br>
happens to be the codebase that 3.2 stable will be branched off of.<br>
For clarification: 3.2 stable will not include Harley features afaik.<br>
What I describe is being accomplished using standard, good development<br>
practices and maintaining various Harley integration branches which<br>
are, in turn, kept rebased against the current HEAD. A basic<br>
understanding of Git version control would probably help clarify the<br>
answers to your questions.<br>
<div class="im"><br>
><br>
> Also, I believe that code will be released more frequently from PTFS than<br>
> every 6 months. It is just that any given piece of code is going to be<br>
> tested by the PTFS customer base first. However, I believe their release<br>
> cycle will be more frequent than 6 months (though I don't remember the<br>
> frequency).<br>
<br>
</div>All of this us pure conjecture until we either a) hear from PTFS<br>
directly (Shawn, where are you?) or b) time reveals the truth.<br>
<div class="im"><br>
><br>
> How do other vendors develop their code?<br>
<br>
</div>In public git repositories. This has been discussed many, many times<br>
on the list. You may see many of them here:<br>
<a href="http://wiki.koha-community.org/wiki/Public_Git_Repositories" target="_blank">http://wiki.koha-community.org/wiki/Public_Git_Repositories</a><br>
<div class="im"><br>
> What is harely if it is not a<br>
> branch?<br>
<br>
</div>Harley is at best a very dated topic branch off of some level of the<br>
trunk (read "master") back there somewhere.<br>
<div class="im"><br>
> Is it not considered a branch because it has not been rebased since<br>
> October?<br>
<br>
</div>Technically, any branch is always a branch. However, as time and<br>
distance increase, it really becomes its own trunk (again, read<br>
"master") and so becomes nearly impossible to merge back into its<br>
ancestor without a very great deal of work. It is this "very great<br>
deal of work" that Chris and Galen are doing as they have time. And it<br>
is true that this work is work that the original developer's should<br>
have done if they were interested in being responsible members of the<br>
Koha community. Also, the work being done by Chris and Galen in this<br>
regard is work most devs would be expected to be paid for. By<br>
integrating Harley code back into the official master, these two are<br>
saving PTFS hours of labor and, of course, lots of dollars... all for<br>
"free."<br>
<div class="im"><br>
> (These are sincere questions on my part.)<br>
<br>
</div>HTH.<br>
<br>
Kind Regards,<br>
<font color="#888888">Chris<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Vicki Teal Lovely<br><br>Helping our 52 member libraries provide the best possible service to the public.<br><br>ILS Project Manager<br>South Central Library System<br>
Madison, WI<br><a href="mailto:vtl@scls.lib.wi.us">vtl@scls.lib.wi.us</a><br>(608)242-4713<br><br>