Anyone have any insights on when we might see the next beta of 4.0c?
We haven't yet decided if it will be tomorrow (right before the long weekend!) or next week.
Anyone have any insights on when we might see the next beta of 4.0c? We haven't yet decided if it will be tomorrow (right before the long weekend!) or next week.
TOMORROW!! Please, please, please! I'm assuming the collections-crash bug will be one of the fixes...I hope!
If its not going to be tomorrow could you at least give a spoiler for any new feature that may be coming in it, if any....
I say tomorrow with a large disclaimer warning for the faint of heart.
Bradley,
I hope that you are not seriously considering releasing the Beta before the long weekend.
In my opinion, a release is not ready until there are the people in place to deal with problems arising from unexpected critical flaws. As there will be no one in place over the weekend, this Beta is not ready for release.
I vote tomorrow too!
Perhaps a disclaimer should posted in the Beta forum: All those who can't afford any potential problems can cancel the installation or turn Internet off.
Come on Bradley, What could possibly go wrong?
We haven't yet decided if it will be ... next week.
Ooo that would make Monday a big day: Zondervan stuff AND a new beta!
I vote for tomorrow. It is beta software. Use the stable version if the beta crashes. And if it will not be released, throw some tidbits our way regarding the new features and bugs fixed.
If your feature is not included or your bug fixed, please be patient.
I vote for tomorrow. It is beta software. Use the stable version if the beta crashes. And if it will not be released, throw some tidbits our way regarding the new features and bugs fixed. If your feature is not included or your bug fixed, please be patient.
Preach it! Warn that the Dam is about to break to give people who would rather wait till Monday time then open the flood gates!
A beta version is unsupported software (almost by definition). If we do release it tomorrow, it's because we consider fixing the known bugs (that are preventing current beta testers from using the software) to be a greater benefit than the risk of introducing new bugs.
Installing the update is optional; if you require Logos employees to be "in place to deal with problems arising from unexpected critical flaws" then I suggest you simply avoid installing it until Monday morning (PDT).
Can we find out if there are any new features? If it is just bug fixes, I will wait til monday.
Jim
There ya go! That's what I like to hear!
Tomorrow sounds good to me. [:P]
I don't usually post in response to opinions, but seriously, have you done beta testing before? (1) You install the updates when you want and (2) You don't beta test on your "production" machines. If you do beta test on your work machines (I do) then you just need to be prepared for the consequences. After all... Logos writes in their Beta disclaimer:
IMPORTANT: Logos 4 Beta releases are beta software. They may corrupt your computer or delete your data. The Passage Guide, searching, or viewing books may stop working. We recommend installing Logos 4 betas only on a dedicated testing machine.
If you ask me all of those would be considered "critical" flaws. So basically, if you don't want to risk encountering a critical flaw you should probably wait until the updates are posted as a release. It seems like sometimes people want to do beta testing just to get software faster and forget that it is a test version, not a preview version.
It seems like sometimes people want to do beta testing just to get software faster and forget that it is a test version, not a preview version.
The 1730 posts indicated under my name do not include the 1000 or so posts which I made during the Private Beta. Either way, this would suggest that my involvement with Logos v4 goes far beyond wanting just to get software faster.
Hi Bradley -
I am not sure how I got beta 2 on my computer, but have you seen this bug?
http://community.logos.com/forums/t/14671.aspx
Thanks!
john
Installing the update is optional; if you require Logos employees to be "in place to deal with problems arising from unexpected critical flaws" then I suggest you simply avoid installing it until Monday morning (PDT
Trouble is, the beta forum shows up on the forums home page, so all the non-beta users are scared spitless when a beta flaw wipes out the L4 beta installations and hundreds of posts over a weekend show up documenting the damage. But, this is the business plan that Logos has chosen, they are adults and will deal with the fall out of their choices.
BTW, if a beta is released tomorrow, I WILL install it. [:D]
The 1730 posts indicated under my name do not include the 1000 or so posts which I made during the Private Beta.
I thought we got our count with pointless posts and making fun of each other.... :-)
You're not helping
Some say tomorrow, others say next week. Bradley make it easy on yourself. Release it tonight. [:)]
A beta version is unsupported software (almost by definition). If we do release it tomorrow, it's because we consider fixing the known bugs (that are preventing current beta testers from using the software) to be a greater benefit than the risk of introducing new bugs. Installing the update is optional; if you require Logos employees to be "in place to deal with problems arising from unexpected critical flaws" then I suggest you simply avoid installing it until Monday morning (PDT).
I know Bradley and I will wait.... It just seems that so many Friday releases of resources and of software (Beta and otherwise) have gone bad....
During the Private Beta, most releases were made on a Monday. This allowed any critical flaws to be quickly acknowledged and subsequently eliminated. It seems that it is only since the Public post-release Betas that we have seen so many Friday drops....
Do whatever you will (as you would have anyway)
I am not sure how I got beta 2 on my computer, but have you seen this bug? http://community.logos.com/forums/t/14671.aspx
What you have isn't the real beta 2 (and I'm not sure how you got it); I have replied on that thread.
A beta version is unsupported software (almost by definition). If we do release it tomorrow, it's because we consider fixing the known bugs (that are preventing current beta testers from using the software) to be a greater benefit than the risk of introducing new bugs. Installing the update is optional; if you require Logos employees to be "in place to deal with problems arising from unexpected critical flaws" then I suggest you simply avoid installing it until Monday morning (PDT)
Installing the update is optional; if you require Logos employees to be "in place to deal with problems arising from unexpected critical flaws" then I suggest you simply avoid installing it until Monday morning (PDT)
Release it - it's only a beta and Australia & New Zealand is on holiday from Friday thru Monday anyway[:P]
Just tell people to turn off Auto Downloading until next week or they hear that it is OK.
Today Today Today!!!
So I think Dave is saying we have 4 whole days to play with it, break it, fix something, break it again, reinstall it a few times, and maybe even read some scriptures before thinking of work on Tuesday morning ...
Bring it on please ... (if its ready to go)...
A beta version is unsupported software (almost by definition). If we do release it tomorrow, it's because we consider fixing the known bugs (that are preventing current beta testers from using the software) to be a greater benefit than the risk of introducing new bugs. Installing the update is optional; if you require Logos employees to be "in place to deal with problems arising from unexpected critical flaws" then I suggest you simply avoid installing it until Monday morning (PDT). I know Bradley and I will wait.... It just seems that so many Friday releases of resources and of software (Beta and otherwise) have gone bad.... During the Private Beta, most releases were made on a Monday. This allowed any critical flaws to be quickly acknowledged and subsequently eliminated. It seems that it is only since the Public post-release Betas that we have seen so many Friday drops.... Do whatever you will (as you would have anyway)
But releasing on a Friday also requires those of us who are afraid of "Friday breakage" to shut off the internet connection for Logos, because the update is automatic. I would humbly suggest that you review the dozens of threads about Friday problems and NOT release it on a Friday. Logos track record on this is less than stellar.
+1...I'd personally go even further and say that if you can't afford to be "put out of commission" by some unforeseen critical bug, then you shouldn't be running beta software at all. You should be sticking the the stable code.
Unless I'm missing something, I've NEVER seen the beta forum on the forum home page. It might be because I'm not on the beta cycle...I'm not sure. I always have to do a search to get to the beta forum.
But releasing on a Friday also requires those of us who are afraid of "Friday breakage" to shut off the internet connection for Logos,
Is it not possible to simply type "set update to default" in the command bar, or is it the case that once your working with a beta default doesn't mean download only release versions?
These posts show up under "Recent Topics" on http://community.logos.com/forums/
This is where I usually go to first see what's recent, if there's anything new in my discussions, and if anybody's questions are unanswered.
The command would be set update channel to default. I'm not sure that would prevent an update or not, if you're already in the beta. But I think it does prevent it.
Thanks for correcting that most important omission. [:$]
But releasing on a Friday also requires those of us who are afraid of "Friday breakage" to shut off the internet connection for Logos, because the update is automatic.
No, just turn automatic updates off (I always have it set to 'off'). That way Logos notifies you of the update, but won't download it without your permission.
Count me in for a Friday drop if you are ready, Logos. I expect ZERO support on this. I understand it is a Beta, and have read the warnings, etc.
I am amazed that anyone would expect support for a voluntary Beta.
Jerry
Count me in for a Friday drop if you are ready, Logos. I expect ZERO support on this. I understand it is a Beta, and have read the warnings, etc. I am amazed that anyone would expect support for a voluntary Beta. Jerry
[Y] +1
They will be off Good Friday
Logos decision makers...
If you drop it today that will give us more time to play around with it, collect our bugs, and maybe even figure some things out on our own. In other words, we may come to realize that some of the things that we first thought were bugs were not and weed them out of our bug reports, which of course would mean less for for you in the end. [;)]
A shameless appeal from my selfish side to yours....
Hey Bradley and Logos et al, just pull the trigger at your command. I'll down load the Beta on my main system regardless. I've been Beta testing quietly for a long time. So I know the consequences and believe me the benfits of running the beta far out way the "sky is falling" fanfare of a new bug introduction. I've been hit by a few of the bugs and they are annoying yes, but you folks get it fixed as quickly as possible.
So release the beta whenever, doesn't matter to me.
Oh BTW have a great long weekend in celebrating Ressurrection Day!! [:D]
Installing an updated program always requires manual intervention: either you have to click the tooltip that says an update is available, or you have to click "Yes" at startup on the dialog that prompts you to install an update.
Only resource updates get installed automatically (once downloaded) by restarting the program.
It's not necessary to turn Internet Use off; as other posters have noted, you can disable "Automatically Download Updates" for the weekend. (And even if you did download the update by mistake, it wouldn't get installed automatically, as noted above.)
Is it not possible to simply type "set update to default" in the command bar, or is it the case that once your working with a beta default doesn't mean download only release versions? The command would be set update channel to default. I'm not sure that would prevent an update or not, if you're already in the beta. But I think it does prevent it.
The "default" update channel for a beta release is the beta channel, so that the program (by default) keeps updating itself.
You can explicitly override this by entering set update channel to stable. If you do this (not recommended) you will stay on Beta 1 and not get any further updates until 4.0c is released to all users (via the "stable" channel). If you do want to do this for the weekend, you can undo it by entering set update channel to default; this will return you to the system default for the program.
I have downloaded the Beta ie 4.0c Beta 2
BUT the "phrase" above after the release numbers is missing.
So then I also entered"set update channel to default" into the command bar.
No change.
What am I "not" doing?
WHY do I NOT have the phrase "(Update Channel: beta)" showing after the bracket containing (4.03.3.8065)?
[My text is ...4.0c Beta 2 (4.03.3.8065) copyright etc...]
I have downloaded the Beta ie 4.0c Beta 2 BUT the "phrase" above after the release numbers is missing. So then I also entered"set update channel to default" into the command bar. No change. Wha tam I "not" doing? WHY do I NOT have the phrase "(Update Channel: beta)" showing after the bracket containing (4.03.3.8065)? [My text is ...4.0c Beta 2 (4.03.3.8065) copytight etc...]
Wha tam I "not" doing?
[My text is ...4.0c Beta 2 (4.03.3.8065) copytight etc...]
If you have explicitly assigned your update channel to beta (or to stable), you will see this. If you set your update channel to default you won't see it.
Dear Richard:
Edit} If you set your update channel to default you won't see it.
Is that not just the opposite from Bradley's instructions? ie is he not saying that "default and "beta" are the same?
What do you htink I should set this too in order for the extra phrase to be addedin the "About" info?
6116.Doc2.docx
I need to know this so that I do not "mess up" my "Regular" non-bata version
[Note - every thing below was entered before the Edit]
the command which I use for this beta machine is:
"Set Update Channel to Default" (without quotes)
Therefore, I feel it should clearly also indicate "Update Channel Beta"
It does not.
(It merely indicates that I do have the beta)
I am confused. Please 'help" me see through this.
Thanks,
Dear Richard: the command which I use for this beta machine is: "Set Update Channel to Default" (without quotes) Therefore, I feel it should clearly also indicate "Update Channel Beta" It does not. (It merely indicates that I do have the beta) I am confused. Please 'help" me see through this. Thanks,
All I can tell you is what I observe. I have the update channel set to default, so even though I'm using the beta, and the default channel for a beta is beta, it doesn't show anything. If while running the beta I explicitly set my update channel to beta (or stable), that will show on the help/about page.
In other words, it only shows something other than default, regardless of whether you are running the stable or beta release.
EDIT: I think this answers your post "edit" questions above as well.
The beta forum shows up as a link all the way down at the bottom of the Logos 4 forum. It's hidden out of the way intentionally so that non-beta users don't accidentally stumble on it. But the beta forum posts still show up in the Recent Topics list anyway.
Well, all that i know for sure was that during the last beta before todays update I had the following phrase:
"Update Channel Beta" (ie. same phrase visible in other poster's screenshot).
Now I do not, and it "worries" me.
Thanks
[edit] and the reason it worries me is that when the last beta downloaded, my "regular" version upgraded to beta "seemingly" on its own. And yes, I realize that is probably a very separate issue. But I do not want to do anything "silly" that is going to mess up another version (either beta or regular).
Hello Steve,
Have you tried typing "Set Update channel to beta"(without the quotes) in the command bar?
THANK YOU!!! Yes!
Thank you both, to Jannie and to Richard.
Although still very "confused" I now have my phase "(Update channel:beta)" returned to me.
- Anyother thoughts on how to keep my non-beta versions "safe"?
