Is there a link to where the beta changes are noted for the sever?
How does one sign up for beta channel?
How "beta" is it? Like unstable nighly builds, or actual beta, or release canadite status?
Ill take the lack of a reply that there is no change log for beta?
Or i'm blind and cant find the thread for it....
There's no central location for the pre-release's notes for Channels DVR Server. Fixes are generally communicated on the threads where the issues are brought up.
Any major feature additions usually get their own threads for discussion.
That...doesn't make much sense.
The update pulls from same URL does it not?
There does not appear to be but a couple at most devs working on this software..
SO any changes made to code, and any new builds made, should be dumb easy to notate changes in a change log/code commit thing. It like a requirement for things like Github far as i been told. If a software dev or programmer does not note changes/updates they make and keep well structured and detailed comments in the code, that is sloppy/lazy and can soon make it very unmanageable for anyone else that ends up working on the code. (my super strict computer programmer instructor from my college days would not be happy..lolz) How would u the dev, even keep track or remember if you fixed or changed something already, or so that one person doesn't mess with something else another has coded.... if you don't keep track.
One thing that is great about Emby (my previous used software), the few devs on that post each change or modifications easy to see, even on beta version. This is something Channels really needs to improve upon. It is not that hard and is pretty much a most basic of things for any software productions.
There's no central location for the pre-release's notes for Channels DVR Server
Sorry about that typo.
Of course we know what changed. What I'm explaining is that there's no central location that we publish these notes anywhere at the moment.
If you're weary of what is included in the pre-release, feel free to stay on the general release, it has fully documented release notes.
As explained in the past, the pre-release is generally just bug fixes related to issues brought up in these forums. The issues are generally very specific the to user that has brought them up. When we solve them, we post back to the thread and ask them to update to the newest pre-release.
The pre-release is not a beta, and not treated as such. It's a release that allows us to solve issues for users very fast and get it in their hands very fast, all without having to do a full roll-out to every Channels fan.
1 Like
A sticky/pinned thread is a good central location...there is the solution that that issue/
But what is "them"??? I just updated to 2020.01.27.0055 and i see a new "Local Content" section.....surprise!!! i have no idea what that is. But having a sticky thread of changes would tell me at least something of what to expect before i update, or help me decide to update or not.
U are saying, u expect users to have to read and follow every thread on here of a user having an issue of any sort, and find buried in there somewhere, maybe, that u make some sort of change or fix in the build. That, have u thought, such a change could affect or cause a new issue for some other user that updated, but has no idea that something or what was changed, so they then report an issue that then u have to chase down......sounds like a big waste of time and is very inefficient. And frustrating to the user.
If you keep achangelog for the cumulative stable release versions, then there is no reason those same change notes can not be posted after each change in the pre-release versions as they increment.
It is really not that hard, takes like 10 secs to copy/paste build number, and type a few quick lines #xyz issue was changed in a sticky thread. and it is common practice for even software that has nightly even hourly builds....take a look at Emby server github and see how they do it.
Then why is the tags on here labeled as "DVR Beta"?? Why is this section where these "pre-release" versions are mainly discussed titled "Beta Community"?
Not trying to be mean or flamey....i just don't understand your distain and rejection for keeping a public changelog for your "pre-release" builds.
We've been writing software for a very long time and understand how to communicate things very well. As I've said, we don't consider the pre-release a public beta.It does not get published with a regular schedule. It exists to fix bugs for specific users that are having issues. Think of it like a hot fix. We make the fix, roll it out, and then ask them to update. This way users with weird bugs can get them fixed right away without us having to roll out a full upgrade to every single user, none of which usually have the unique problem.
We release pre-releases multiple times per day. Once there are many changes in the pre-release, we then decide when a public release should ship out. We release that with a full change log.
As for the Imports feature you found, as I said earlier, when there is a new feature on our pre-releases, we open a thread about it for discussion.
Again, if you are concerned with running software without detailed notes, we suggest you stay on the normal dvr release.
every hot fix, no matter how often a build is made, for every software i have used in the last 30yrs, has a changelog. just saying....
How do u get back on the normal release once you have pressed and held the update button?
The DVR server regularly checks for stable releases, and will auto-update to the latest stable release. Even if you are on a prerelease, you will be automatically updated to the stable release when it is available.
Thats good to know, but does not answer the question you quoted.
I gather there is no easy way to downgrade the server then?
You didn't specify.
If you wish to downgrade, you can stop the server. Then go into its directory (the parent directory of the data folder) and change the latest link to point to the version you wish to go back to. Now start the server back up, and you're all set.
I'm sure it wasn't intentional, but you are coming across a bit harsh. While I would like a change log too, it is only because I am excited to see how the Devs are improving the product. I think they have been very fair with their explanation here though. More than you would get from most developers.
2 Likes
The exactly why most of us here want to see what active changes are being done and be informed. No such posts or visible developmental progress shows a product this is not actively being developed or supported. Case in point, the devs that do Emby, or Ubiquiti or Merlin Asus firmware, to the Download Manager I use or apps on my phone, all produce changelogs with each build (release, P.R, Beta, Alpha)....its an industry standard practice. (Google also now is enforcing dev changelogs in the app descriptions)
It kinda is like i load up today's local news feed and all that is there is "some news happened to day." and that is it. It may or may not be relevant to me what is reported, but I still want the ability to decide that for myself.
It is your opinion to call a simple criticism and suggestion for improvement as "harsh", or something so simple, but yet important to most anyone like me who now rely on this software.
I do appreciate the further explanation given... but it sounds more like an excuse to me. I have expressed my opinion on that, and I am sure others woudl be far more "harsh" then i am apparently am being.
It also is kinda rude, imo, to have ignored the post for 17 days. In one of the posts this is said by the dev "As we grow, and the community grows, we'll figure out a better way to do this." But it does not sound like they are listening very well to me, at least on this specific topic.
Cheers
I wasn’t going to say harsh, I was going to say “Demanding and condescending.” At this point everybody on the forums (including the devs) knows you want change logs. Would that be nice? Sure. However, posting about it repeatedly and going on about how simple it should be is likely not going to improve the chances of it happening. On the other hand, it does lower your standing with the rest of the community.
8 Likes
Meanwhile the devs have been dismissive. Simply because they have been writing software for a long time doesn’t mean their process for doing so cannot be improved. If they can take the time to provide change logs for iOS/tvOS/macOS users, they can do the same for Android/Android TV users.
A “hotfix” process doesn’t exclude notes or change logs. It simply doesn’t. The claim is that these are simply rolling bug fixes to address things brought up in this forum. Common sense dictates that it would be valuable to be able to identify those bugs and then track feedback from users after those bugs have been addressed. The logic laid out in this thread indicates that those bugs are apparently addressed, but no one bothers to tell users when they have been unless they use certain devices. The same can be said for new or additional features that are first tested in this format. They just randomly appear with little to no explanation.
Also...and I can’t believe I have to write this...if you don’t consider it to be a beta process...maybe don’t put beta in the file name of the release?
We aren’t just out here whining about some free app or software. We are paying for this. Some small degree of notice of change from one version to the next is not at all unreasonable.
2 Likes
But you aren't paying for "this" you're paying for stable release and with those stable releases you also do get release notes, the betas are provided to you at no additional cost and is an opt in bases. So with betas you aren't entitled to anything at all. if you want release notes in a any you like I'd suggest downgrading back to the stable version.
3 Likes
Please show me where a differentiation is made between whether I am paying for access to the stable version or the beta version.
Let’s not also forget that the devs don’t consider what they call a beta to actually be a beta...even though they call it a beta.
1 Like