Next Beta?
I'm watching with anticipation of the next beta...as I'm not brave enough to go with Beta 1. Any clue when the next patch is expected? And...THANKS LOGOS TEAM!
Comments
-
I've never timed the distance between betas myself because it does fluctuate. Though Logos has certainly become conscientious about not posting a new beta on Friday when people may be finishing sermons etc.
Sarcasm is my love language. Obviously I love you. 0 -
Waiting for a 2nd or 3rd beta does not guarantee a safer experience. Occasionally a later beta will have a showstopper not present in earlier betas. If you are sure you want to run a beta, have read all the warnings, and you have a safe backup installation of a stable version, the best thing to do is monitor the beta forum for about a week after the beta is released for any showstoppers, if you don't see any major issues reported and none of the features you regularly use have problems then install that beta, and then immediately turn off updates.
Beta 1 is amazingly stable for the amount of work done on it. I haven't seen any showstoppers or anything that majorly affects features I use on PC. I have not paid as much attention to any MAC issues.
You may wish to wait though for advice from one of the more experienced users.
0 -
...Randy W. Sims said:Waiting for a 2nd or 3rd beta does not guarantee a safer experience. Occasionally a later beta will have a showstopper not present in earlier betas.
Randy W. Sims said:You may wish to wait though for advice from one of the more experienced users.
You have answered the question admirably IMHO.
Sarcasm is my love language. Obviously I love you. 0 -
Jackie Watts said:
Any clue when the next patch is expected?
If history repeats (about every 2 weeks), then anticipate 5.3 Beta 2 later this week.
Wiki => https://wiki.logos.com/Mac_Release_Notes_and_History#Mac_Beta_Release_Notes_and_History has Windows and OS X Beta release dates since 4.2a release.
Keep Smiling [:)]
0 -
Randy W. Sims said:
Waiting for a 2nd or 3rd beta does not guarantee a safer experience. Occasionally a later beta will have a showstopper not present in earlier betas. If you are sure you want to run a beta, have read all the warnings, and you have a safe backup installation of a stable version, the best thing to do is monitor the beta forum for about a week after the beta is released for any showstoppers, if you don't see any major issues reported and none of the features you regularly use have problems then install that beta, and then immediately turn off updates.
Beta 1 is amazingly stable for the amount of work done on it. I haven't seen any showstoppers or anything that majorly affects features I use on PC. I have not paid as much attention to any MAC issues.
Randy,
in principle one shouldn't run beta as production version - unless that beta fixes a production-relevant bug. Someone should especially tell young pastors that it's not a good idea to update to a beta version just before starting the study phase for the sermon due the next day (and the worship leaders/church technicians that it's not a good idea to upgrade to a beta OS Sunday morning at 09:00 am. when service starts at 10:00 am). Even if the beta 'only' triggers a complete reindex, it may leave the machine useless for hours.
So for those who ask about running a beta "safely" the first answer should be: don't run it. period.
What is a "showstopper" depends. In this beta, I personally see two major issues:
- the beta install in a dedicated account broke the stable version running on the same machine. This is something that should never happen and it underlines the point that even those who try running it safely might be hit by unforeseen side-effects. Even though there seems to be a workaround, there was a time when one was relegated to either run with the beta, wherever it may lead, or invoke a restore from an earlier point in time (if possible). This is a situation one doesn't want to be in.
- the current beta breaks PB compiling for some users. This may be relevant only for a small subset of users, but for someone who relies on this feature (e.g. students with a teacher giving out the syllabus in *.docx incrementals and the students compile them as PBs) it's a showstopper.
In these cases, I think your advice is very good. Not the beta number, but listening out for a week or two what others report and then installing this "in the field for some days"-version if no adverse reports came in, is a prudent way - on the other hand, if someone's showstopper is e.g. in the handout feature, and no one from those posting in beta had tested this feature (or, if so, belonged to the group of users for whom it breaks), then there is no adverse report even if the beta is buggy. So again: if you need to prepare service leaflets with the handout feature, don't move to beta (or at least do so on Sunday afternoon rather than Saturday).
Have joy in the Lord!
0 -
NB.Mick said:
What is a "showstopper" depends. In this beta, I personally see two major issues:
- the beta install in a dedicated account broke the stable version running on the same machine. This is something that should never happen and it underlines the point that even those who try running it safely might be hit by unforeseen side-effects. Even though there seems to be a workaround, there was a time when one was relegated to either run with the beta, wherever it may lead, or invoke a restore from an earlier point in time (if possible). This is a situation one doesn't want to be in.
- the current beta breaks PB compiling for some users. This may be relevant only for a small subset of users, but for someone who relies on this feature (e.g. students with a teacher giving out the syllabus in *.docx incrementals and the students compile them as PBs) it's a showstopper.
- For one user corrupted a number of his databases after every program start.
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
Another thing to factor in is that once you are on the beta program it is difficult (though not impossible) to leave it until the next stable version is released.
And just because Beta 1, for example, may not cause you an issue it is possible that such an issue would be introduced in beta 2.
So it could be worth holding off on each beta download for a bit.
Edit: apologies. Just noticed that Randy had already made this poimt above!
0 -
That all said: Bradley's answer regarding the PB compiler issue gives me hope that a new beta is due to be out soon! [:D]
Have joy in the Lord!
0
