As I said last week, we’re in the final stages of testing Visual Liturgy Live, and our development team now have the Release Candidate ready. That’s the version of the code that\u00a0is a “candidate for release;” in other words we put this version\u00a0through its final exams and\u00a0then allow it through to the release process, which culminates in the pressing and packaging of CD-ROMs.\u00a0At this stage we wouldn’t expect to find any major problems that would stop the show.<\/p>\n
The work that’s been\u00a0going on since Friday last week is in three parts: adding content to the pages of www.visualliturgylive.net<\/a>, testing the subscription and registration services, and preparing the database to be pressed onto the\u00a0CD-Rom with the software.<\/p>\n Many of you know that Church House Publishing relies on a lot of expert help in the user community, much of it from volunteers. We’re fortunate to have a team of people who are both technically and liturgically literate. A number of these people have made invaluable contributions to VL Live, editing content as diverse as hymn indices, seasonal material from new Common Worship publications, and the lectionary database held within VL Live. It’s this diverse content from numerous sources that we’re pulling together into one\u00a0database, which is being checked and tested before we release it.\u00a0<\/p>\n After release, we’ll\u00a0be publishing a lot of material about how to use features like Smart\u00a0Templates effectively, and those of you with an inclination to get under the hood of\u00a0VL Live\u00a0may\u00a0well\u00a0see and learn more about how that data hangs together if you follow some of our examples later in the year.<\/p>\n \u00a0I’ll keep you up-to-date with our testing progress as the week goes on…<\/p>\n Andrew<\/p>\n Andrew Sweeney<\/span> \u00a0<\/p>\n \u00a0<\/p>\n","protected":false},"excerpt":{"rendered":" As I said last week, we’re in the final stages of testing Visual Liturgy Live, and our development team now have the Release Candidate ready. That’s the version of the code that\u00a0is a “candidate for release;” in other words we … Continue reading
\n<\/span>New Media Manager<\/span>
\n<\/span>Church House Publishing<\/span>
\n<\/span>\u00a0<\/p>\n