|
Aloha, Peter.
Actually, during a rebuild, neither my main site or the beta site are "out", if all goes well. If all doesn't go so well, the beta site might go down, but not the main site. Even a full rebuild is done one module at a time, with all of the pieces of each module done consistently, so that at any time, you can pull one or more modules from either repository. The only reason my whole repository went down for a rebuild in the past was that (1) there was a major defect in the rebuild process AND (2) I didn't notice it and halt the process timely (due to such distractions as being at a conference and otherwise busy most of the time). The main purpose of the eBible.org swordbeta repository is to run the full process, as it currently exists, on a repository I can access from mobile devices, and try it out "live" before shunting those changes over to the eBible.org sword repository. The full rebuild paradigm has many advantages, including consistency of output quality for all modules and speed. The quality issue is important. Frankly, I don't expect much feedback on most of the minority language Bibles, even if there is a problem with it. But if the KJV or WEB have a problem, I expect to hear about it. (And I do, regularly-- and fix such problems when they are verified.) When it is the same process and the same input format, I can expect quality improvements in the process to benefit not just the English translations, but all of them. There are two classes of "fix": those affecting the process, which involve a total rebuild of the repository to correct, and those affecting the source files of a particular Bible translation. Those will be handled with a partial rebuild. These are usually an update of a translation work in progress, correcting a typo, or some similar thing, with no changes to the process. There is a third thing that can trigger a repository rebuild, and that is regression testing of the Haiola software. In this case, the eBible.org/sword repository would not be updated, but the eBible.org/swordbeta repository would be updated. Normally, there should be no difference between modules in the swordbeta and sword repository in that case, except maybe the module version number, which currently autoincrements for each build. So, Peter, I understand your concern. I think we have it covered. There were definitely some growing/labor pains in getting the eBible.org repository up and running, but I think it is OK, now. At least it is working for me. The eBible.org/sword repository should be available at least 99% of the time. Because of the size of the repository and the frequency of updates, it is a good idea to refresh the list of available modules before downloading or updating any modules. The full rebuild with all of the corrections I know to do has now been done. The repository pair is at rest and synchronized. The engKJV1769, engKJV2006, and spaRV1909 look a lot better, now, as do the Greek and Hebrew modules. The "about" pages look much better, too. And, some rare but troublesome missing spaces in the rest of the modules have been restored. Haiola is at rest, at least until I do some regression testing and testing of new PDF conversion code, or until I enter some language updates to the WEB and some typo corrections to the KJV Apocrypha/Deuterocanon. On 08/28/2015 09:34 AM, Peter von Kaehne wrote: Michael, What bugs me in this process is emphatically not the need for ongoing fixes. That is entirely expected. But i am concerned that each fix results in a total rebuild, which takes your site out for some 24 hrs or so.I would think partial rebuilds should become the norm, no? Peter Sent from my phone. Apologies for brevity and typos.On 28 Aug 2015 6:37 pm, Kahunapule Michael Johnson <kahunap...@ebible.org> wrote:On 08/28/2015 04:08 AM, David Haslam wrote:Michael, Thanks for the announcement (and your private emails to me). Leaving only until tomorrow for more beta testing (even on my own reported module issues) is rather tight!Yes, it is rather tight, but I'll be testing too. It isn't like we can't fix problems you find a day or three later. Quality control improvement is a continuous process. My threshold for transferring from eBible.org/swordbeta to eBible.org/sword is just that it is an improvement, not that it is perfect. A perfect Sword repository doesn't yet exist, but we can keep improving. -- Aloha, Kahunapule Michael Johnson MICHAEL JOHNSON PO BOX 881143 PUKALANI HI 96788-1143 USA eBible.org MLJohnson.org Mobile: +1 808-333-6921 Skype: kahunapule_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page --
Aloha,
|
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
