Replies: 3 comments
|
Adding a note here about another major change in 6.1.0 for MacOS users only. The Application/Package code-signing certificate is changing for 6.1.0. This is required to free-up @Palakis from using his personal account while his involvement with the project is reduced since @paulpv came onboard. Thanks @Palakis for this project Moving forward the team at EPEAK Studio will provide the Apple Developer support & requirement. As an open-source project it is expected that some changes occurs in the span of the project's lifetime, theses changes are made to have a more sustainable maintenance and avoid deadlock. Expected impact of the code signing change** Only MacOS** is impacted. |
|
All changes now available in 6.1.1 : https://github.com/DistroAV/DistroAV/releases/latest |


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is a topic to communicate & discuss some of the upcoming changes in DistroAV 6.1.
DistroAV 6.1 will be the second "major" release from a set of new maintainers & contributors
Global vision:
A review of the most common requests
The past months (actually almost a year), we re-visited and updated all the open issues, some dating back close to this project inception.
We closed a LOT of them as their either were fixed, too old to be relevant, undocumented or nu-reproducible.
Reviewing all the issues also helped to better frame & understand the challenges that you (as a DistroAV) encounters. There was a disproportionate amount of low-effort, undocumented support-requests that forced us to be more direct when similar requests come in.
This culminated with a set of improved Issue templates submission, with clearer expectation and simpler data to process.
As it's clear(er) and simple(r), this should help identify possible bug and allow to reproduce them much faster, saving time for all contributors and ultimately allowing faster updates.
As this is a volunteer project, bug and support request will focus on the latest available DistroAV version. (for those of you still on 4.X versions of OBS-NDI, please upgrade as soon as possible as we consider this codebase obsolete, and are not testing it with any new OBS release)
What to expect for DistroAV 6.1?
Updated Minimum Requirement
Why is this change necessary ?
There are changes integrated in OBS 31 that split the configuration files and we are following the guidelines set by the OBS team for a sustainable OBS-user community.
NDI v6 has been widely available for months now and proven reliable. The codebase in DistroAV 6 already integrate with NDI v6, even tho we did not leverage new feature and code optimization (yet), this will be a possiblity at "anytime" with DistroAV 6.1.
Making the project sustainable
As said in intro this project is maintained by volunteers, some of us dedicate their personal time or are lucky enough to have some hours from our work allocated to contribute to Open Source project like DistroAV.
Here are some ways to contribute:
-Using this in a place of worship? Consider a financial donation as well.
When ?
There is no release date planned yet for DistroAV 6.1, but should be expected in the coming weeks.
All reactions