Replies: 5 comments 14 replies
-
|
Yes, it would be great when translating to see if I got it right... |
Beta Was this translation helpful? Give feedback.
-
|
A suggestion: The beta version could only be available to those who indicate the beta option in the M3. This would make testing easier. For example, I always test it at home, and then install it on the KH. If you can choose to use or not use the beta version, that would be great. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I'm envisioning a toggle in the settings that would allow you to subscribe to the beta releases for auto updates. Still have to fogure out how to though. |
Beta Was this translation helpful? Give feedback.
-
|
Seems simple enough. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I found that too, but ideally I'd like to automate it to release a new beta release for every commit to the master branch. |
Beta Was this translation helpful? Give feedback.
-
|
Of course you do 😆 |
Beta Was this translation helpful? Give feedback.
-
|
I figured it out! See my fork. It bumps the package.json version (23.2.1 -> 23.2.2-beta.0 -> 23.2.2-beta.1), creates a draft, builds the app, publishes the draft. It executes on every commit, but fails on the |
Beta Was this translation helpful? Give feedback.
-
|
As regards the vote - On my home PC I don't mind beta versions as I trial and test and become familiar with the latest features using my home setup. At the Kingdom Hall of course we would only use stable releases. 😁 |
Beta Was this translation helpful? Give feedback.
-
|
Completely valid! I currently have a nice automation in the works that would release a new beta version every half hour (if there are new changes to release) which you would automatically receive by turning a |
Beta Was this translation helpful? Give feedback.
-
|
Can this beta be turned off by the VO when using the syncrothingie? |
Beta Was this translation helpful? Give feedback.
-
I'm guessing not, since this is a per computer setting. |
Beta Was this translation helpful? Give feedback.
-
|
We could make it lockable, but then no one connected to the congregation server can enable it for themselves. Not sure that's what you want. |
Beta Was this translation helpful? Give feedback.
-
|
Most likely it will not be a problem. Just need to inform all users at KH that this is a no go... Try it home but not at KH. |
Beta Was this translation helpful? Give feedback.
-
|
Good news! We've implemented the beta release feature! A beta version with the latest changes will automatically be released every 12 hours. You can opt in to these releases using a toggle in the App Configuration settings. When enabling this option, you might need to restart the application to start receiving the beta updates. |
Beta Was this translation helpful? Give feedback.
-
@mtdvlpr, About the beta version, is it possible to know [on the M3 screen] what is being tested? Or just following here on the forum? When you click to check the information after the update, it goes to the current default version releases screen. |
Beta Was this translation helpful? Give feedback.
-
|
@e-Feitosa, here is the latest beta information (nothing exciting). The 'more information' button link will be fixed in the next release :) |
Beta Was this translation helpful? Give feedback.
-
|
@mtdvlpr, in the beta version, I didn't find the option to test the zoom meeting integration. And when I installed the version that is Google Drive, the M3 downloads an update and removes the zoom+m3 test option. Would it be possible to include it for testing too, or is it still too "early"? |
Beta Was this translation helpful? Give feedback.
-
|
@e-Feitosa, the automatic beta includes features that have been merged already. Since the Zoom integration isn't merged yet, it's not included. I'll update the Google Drive test version, so that it doesn't want to update. |
Beta Was this translation helpful? Give feedback.
-
|
The Zoom integration test version has been updated :) |
Beta Was this translation helpful? Give feedback.
-
I have been wondering. Some appreciate it when their feature request or bug fix is available before the official release comes out. Currently, these beta/test versions are manually provided by downloading the artifacts from GitHub and uploading it to Google Drive. We could invest some time in trying to implement a (semi) automatic way of providing everyone with the latest changes in the form of a beta release. Before we do, I'd like to know if that's something that you guys want.
8 votes ·
Beta Was this translation helpful? Give feedback.
All reactions