<div dir="ltr">Any particular reason for moving off GitHub onto the CrossWire servers?<div><br></div><div>You might want to look at setting up GitLab for hosting it on the CrossWire server. But I'm not sure I see the benefit of bringing it back?</div>
<div><br></div><div>Chris</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 19 June 2013 12:49, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As long as we follow the advice to have subsequent releases that fix bugs and minor details, I don't see any reason to wait. But I haven't had time to test the new KJV and ESV with it.<br>
<br>
I'll add my voice to a long list requesting branching for the release. Greg has volunteered to manage such. I suggest we take him up on that. Two parts to this: Tagging the release as we always have done and creating a branch before making changes that shouldn't be part of 1.7.x.<br>
<br>
In the next month or so, I'll be moving the JSword git repository to the CrossWire server as the master copy. We'll still use github until we figure out collaboration on the CrossWire server.<br>
<br>
I suggest seriously considering using git for SWORD. I was leery at first that it was YASCC (Yet another source code control) offering no real advantage over SVN. At this time, I won't go into why I'm sold on it. It really isn't part of this discussion. But suffice it to say: it makes branching and using branches easy.<br>
<br>
The only thing that I've noted in the last month is the notion that the module version number is a 3 part number where the third part is updated for conf changes and as such does not require the module to be downloaded again. Does the engine offer support for knowing this or is this a front-end responsibility?<br>
<br>
In Him,<br>
DM<br>
<div class="HOEnZb"><div class="h5"><br>
On Jun 19, 2013, at 4:45 AM, "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:<br>
<br>
> Things have been quiet for a bit. I have all the patches in that are on my todo list. Anyone else have outstanding issues? Now is the time to speak up.<br>
><br>
> Chris, any feedback on my Ralfs suggestion?<br>
><br>
> Peter, still binding troubles? Can you give me your exact commands executed and I'll try them here.<br>
><br>
> David, are you still worried about a mid-verse heading? Did you find one? I know there were a couple in the NASB, as that was the context for the conversation between Karl and I when it came up a while back, but can't remember where.<br>
><br>
> Anything else? Let's push this to completion. I need your help.<br>
><br>
> Troy<br>
> --<br>
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>